[cvsnt] Require Comment on Commit

Network Engineer intnengineer at gmail.com
Wed Mar 21 19:25:08 GMT 2007

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.

I agree completely, useful comments will only come from cooperative people,
but I still need to require the comment on commit, whether it's "correct" or
not is up to management.
The question still stands, "Is it possible with CVSNT to require a comment
for the commit action?" or maybe more accurately, is it possible from the
CVS server to require them. If so, how? Examples?


On 3/20/07, Arthur Barrett <arthur.barrett at march-hare.com> wrote:
> Is the comment "aaa" acceptable?
> I suspect what you are actually trying to do is ensure that users
> committing changes to the repository give some meaningful information
> together with the change. Unfortunately if a user is inclined to not
> supply comments - making the comment mandatory usually causes the same
> user to start using comments like "aaa", "bbb", and "go away".
> You can write a comprehensive comment analysis routine and call it from
> the precommit trigger (which I have seen done).  You can ensure that
> there are at least 7 words, check dictionaries and all sorts of other
> lovelly things.  However anecdotal evidence shows that the same user who
> used to not put any in comment, then upgraded to "aaa" will now simply
> write a little program that extracts random paragraphs from "Alice in
> Wonderland".
> On another group it was proposed that the only effective way of ensuring
> that users enter useful comments is the liberal employ of a large stick.
> Seriously though - there are times when no comment is really required,
> and adding kruft is very rarely helpful.  For configuration management
> to be effective there should however be a relationship between changes
> and other things (like customer requests, project plans etc).  That's
> why CVSNT has a -b and -B flag to relate changes to a tracking number
> and why CVS Suite has integration with Bugzilla.  So whilst cvs ci -m ""
> fred.c may be poor, cvs ci -B 1234 -m "" fred.c is much better.
> Currently you cannot make bug numbers mandatory - but that feature
> should be in the next release (2.5.04) in the next few weeks.
> Regards,
> Arthur Barrett
> > -----Original Message-----
> > From: cvsnt-bounces at cvsnt.org
> > [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Network Engineer
> > Sent: 21 March 2007 07:52
> > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> > Subject: [cvsnt] Require Comment on Commit
> >
> > Is it possible with CVSNT to require a comment for the commit action?
> >
> > Thanks

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