[cvsnt] Comments

Prochazka, Jan Jan.Prochazka at brooks.com
Fri Mar 28 18:40:52 GMT 2008

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 sales@march-hare.com.

With all respect to what was said below. We found that many users
omitted comments when they were not enforced but only very few were
putting non meaningful comments after commits w/o comments were
Moreover, comment enforcing also helped greatly to avoid unintentional
commits from Tortoise.
Best Regards to all,

P.S. search forum history and/or CVSNT help pages for commit enforcement
script examples (I unfortunately do not know the locations out of the

> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Gerhard Fiedler
> Sent: Friday, March 28, 2008 08:53
> To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> Subject: Re: [cvsnt] Comments
> Peter Crowther wrote:
> >> Is it possible to force end-users to insert comments when 
> they Commit 
> >> there files?
> > - Don't bother, because lazy developers will just enter "AAA" or 
> > "Latest version" (and some will work out how to write the 
> script that 
> > does that for them automatically).  You don't just want *comments*, 
> > you want *meaningful comments* - and they're hard to detect 
> > automatically.  User education is far more effective at getting 
> > meaningful comments into the repository.  A cricket bat 
> would seem to 
> > be an appropriate user education tool... :-).
> Ah, the old cricket bat -- I almost forgot that one :)
> On a more serious note, code reviews that include commit 
> comment reviews and making the developers understand that 
> they have to go back and update the comments if they don't 
> add them in the first place (which includes making their 
> projects leads understand that they have to make the 
> developers go back and update the comments and bug them until 
> they actually did it) may be helpful, too. 
> In short, you have to give it priority in the overall process 
> -- up to consequences for the job and payment in serious 
> cases, just like with other forms of sloppy work.
> Gerhard
> _______________________________________________
> 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
> _____________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.

This email message, including any attachments, may contain confidential and proprietary information for the sole use of the intended recipient.  If you are not the intended recipient, you are hereby notified that any use, copying or dissemination of this message is strictly prohibited.  If you received this message in error, please notify Brooks Automation, Inc. immediately by reply email or by calling Brooks US Headquarters at +1 978-262-2400. Then delete this message from your system, without making any copy or distribution.  Thank you.

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook