Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
I am the one developing CVSMailer and I have a mail link on the CVSMailer webpage for this kind of information exchange. No forum, I'm afraid. Concerning your issues: 1. Committing user not in the users file I will see what can be done, I thought thta it was already handled. What is the CVSMailer version you are using? It is visible in the footer of all emails sent by CVSMailer. 2. Issue tracker links Maybe I could have separate CVSMailer.ini sections for the different repositories? Or I could add a new admin file CVSROOT/cvsmailerissues in which the valid settings could be stored? Both of these seem to me a bit cleaner than having separators in a single set of configs. I am now leaning towards something like: [IssueTracking] UseIssueLinks=1 UseCVSROOTconfig=1 and the CVSROOT/cvsmailerissues would contain: [IssueTracking] IssueUrl=http://myserver/mytracker/myissues/WGS-<number> IssueReference=[WGS<number>] etc This way you can fine-tune the settings on a per repository basis What do you think? Best regards, Bo Berglund -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Joe Enfield Sent: den 1 februari 2006 22:06 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] [CVSMailer] 2 questions I hope it is ok asking about CVSMailer in this group... I have CVSMailer setup and running very well. Question 1 - When a user is not in the 'users' file and that user commits a new file revision, no commit notification is sent to the people in the 'loginfousers' file. Can this be changed so that we have a 'default' fall back reply-to email address if the committing users email mapping is not found, and ensure that a commit message email is always sent to loginfousers list? Question 2 - Our organization will eventually have several repositories setup on our cvs server. This will work great with CVSMailer and each cvsroots set of users. However, our Issue tracker will have several 'Issue Number' representations. For example WGS-12345, PRC-12345, etc... And for each of these issue number representations we would have a different URL address. http://myserver/tracker/WGS-12345, http://myserver/tracker/PRC-12345, or even http://mydifferentserver/tracker... The 'issue <number>' is setup in the CVSMailer.ini, not in the CVSROOT admin files. It looks like only one issue number can be defined. Is there anyway this can be modified to (or does it already) accomodate more than one IssueReference/URL? **** Current Example **** [IssueTracking] UseIssueLinks=1 IssueUrl=http://myserver/mytracker/myissues/WGS-<number> IssueReference=[WGS<number>] **** Proposed Example **** [IssueTracking] UseIssueLinks=1 IssueUrl=http://myserver/mytracker/myissues/WGS-<number>;http://myserver /myt racker/myissues/PRC-<number> IssueReference=[WGS<number>];[PRC<number>] Thank you for taking the time, and thank you for CVSMailer. Joe E. _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs