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.
So you mean that a loginfo line like the one below will now work fine?
ALL C:\Program Files\CVSMailer\CVSMailer.exe -l$CVSPID $USER $CVSROOT %{sVv}
It did not when I last tested so therefore I use this:
ALL D:\server\CVSMailer\CVSMailer.exe -l$CVSPID $USER $CVSROOT %{sVv}
/Bo
-----Original Message-----
From: Tony Hoyle [mailto:tmh at nodomain.org]
Sent: den 10 april 2003 19:02
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: Re: [cvsnt] Re: newbie: Cannot create repository
On Thu, 10 Apr 2003 09:32:38 -0700, "Glen Starrett" <grstarrett at cox.net>
wrote:
>Sounds more to me like a very practical practice. In all the reading I've
>done I didn't realize there were so many gotchas with the CVS* add-ons /
>scripts / etc. I mean, I saw a small recommendation (and a stronger one for
>spaces in source file names) but beyond that I didn't see a lot of reasoning
>behind it.
>
>Of course, I've installed MY cvsnt into d:\cvs\cvsnt, with my repository
>d:\cvs\respositiories and temp d:\cvs\temp... all in one spot, nice and
>clean. :)
>
>Perhaps a candidate for updating on the wiki?
>
The executable works fine in "Program Files" and the scripts work fine with
spaces etc. - that's now I have them configured here... I wouldn't really
want to start recommending that people move the executables out of "Program
Files" since that's the place where you're supposed to put installed stuff.
I'd agree the repository should be somewhere without spaces... it's a complete
git to use from the command line otherwise :)
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