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.
Thanks Tony on your respective answers. Looks like I need to RTFM for most of them... Looks like I'll have to wrapper the client side for the cvs add stuff. Is it documented anywhere what the structure of the /tmp/cvsserv... files are, during an operation? There's a whole load of info about the internal CVS files in Section 2.3 but is this it? To date, I've grabbed a tgz of the files during the operation then tried to figure it out from there. Is there a better way? Many thanks for your advice so far. Steve -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Tony Hoyle Sent: November 7, 2005 5:40 PM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] Re: how to get the branch information before cvssteve at diablo-technologies.com wrote: > a) The directory name used prior to altering the cvs repository > when that directory is added > Note: "cvs add <dir>" immediately modifies the repository > (i.e. doesn't require a commit). Also aborting > "cvs add <dir>" in precommand still leaves a CVS > directory behind in the client side called "<dir>/CVS" It's impossible to sensibly abort 'cvs add' in any cvs version at the moment - if anything it's a 2.6 enhancement as it'll require a few changes to the way add works (on the client side too, so you'd have to restrict to 2.6 clients when this happens). > b) The file and branch name used for each file before it is commited. > Note: commitinfo and precommand do not provide this info > (as Bo described below). The tag information is in the current directory when commitinfo is called (I'm surprised Bo didn't mention this). Bo Berglund wrote: > Strangely it is hidden in another section in the cvs helpfile: > > History Browsing/User-defined Logging/The taginfo file > > Don't know why it has been relegated there, though.... > It always was there, even in the old cvshome manual... it's not a commit support file so isn't listed amongst them.