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 beleive commitinfo runs on the server.... but CVS/Entries is client side... so I am confused as to how a commitinfo script / program accesses CVS/Entries when it is invoked ? If this is the case could you elaborate on how to get hold of this inforamtion at commit time in a commitinfo script/program. I would like to restrict commits on a per branch basis... -Richard. -----Original Message----- From: Tony Hoyle [mailto:tmh at nodomain.org] Sent: 15 November 2004 15:27 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: Commit nofify for commit on certain branch Thomas Keller wrote: > Is cvsnt capable to pass the branch tag on which the commit happens > to commitinfo so that a nitty-gritty script could grab it up and decide > whether or not it should send a notification? There isn't one branch tag - there can potentially be a different one for every file of the commit. The CVS/Entries file that the commit script can see has the current tag for each file. > Furthermore if this "merge" commit happens the "unstable" branch > should be set to readonly so that no commit "accidents" happen to > this branch. Not quite so important, but a nice to have. Set a merge ACL on the branch. Tony _______________________________________________ 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