[cvsnt] Re: cannot stat on commit/release woes

Tony Hoyle tmh at nodomain.org
Tue Jul 27 18:16:30 BST 2004

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.

John Kinson wrote:

> We get it here all the time too.  Our production repositories are hosted 
> on Win2k server machines, our development PCs run Win2k (workstation). 
> AFAIK no unusual timezone settings are in effect (we're in the UK in 
> what's optimistically called summertime).  All filesystems are NTFS. 
> Even testing locally (i.e. sspi access to a cvsnt server running on the 
> local PC) has the same problem.  All other cvsnt commands work fine, 
> it's just release that misbehaves.

Odd.. as I can't reproduce it even locally.  There must be a common 
element that's not working.  I'm in the UK too which often causes 
timezone problems to be missed, as I'm in GMT for half the year.

> I would disagree about the release command being pointless though; I 
> frequently check out sandboxes from many different repositories, and 
> when done, want a safe way to delete the directory without accidently 
> discarding uncommitted changes.  "cvs release -d" is *exactly* the right 
> command to use for this.  Or is there an easier way?

I'd normally do a commit first anyway so don't hit that problem.


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