WinCVS version 1.2 is incorrectly reporting that cvs controlled files
are locally modified. Interesting it only does this for some files and
not others. To check out files, I'm using the version of cvs.exe that
comes with cygwin (version 1.11). Any help is greatly appreciated.
Thanks
Chuck
At 10:25 AM -0800 3/8/01, [EMAIL PROTECTED] wrote:
>Content-Type: text/plain; charset=US-ASCII
>Content-Disposition: inline
> ;Creation-Date="Thu, 8 Mar 2001 12:25:20 -0600"
>Content-Transfer-Encoding: 7bit
>
>WinCVS version 1.2 is incorrectly reporting that cvs controlled files
>are locall
> One thing that will cause this is if you have users that
> commit files with DOS EOL characters. I believe the sequence is this:
>
> 1. in wincvs or upon cygwin installation, select the option to
> preserve unix EOL conventions.
I have this set for both cygwin and WinCVS. My interpretat
At 11:34 AM -0800 3/8/01, [EMAIL PROTECTED] wrote:
>Content-Type: text/plain; charset=US-ASCII
>Content-Disposition: inline
> ;Creation-Date="Thu, 8 Mar 2001 13:34:07 -0600"
>Content-Transfer-Encoding: 7bit
>
>
>> One thing that will cause this is if you have users that
>> commit files with
> WinCVS version 1.2 is incorrectly reporting that cvs controlled files
> are locally modified. Interesting it only does this for some files and
> not others. To check out files, I'm using the version of cvs.exe that
> comes with cygwin (version 1.11). Any help is greatly appreciated.
> Thanks
se the WinCVS version of of cvs.exe from the bash command
line.
I wonder whether we should expect a patch anytime soon?
Thanks
Chuck
> -Original Message-
> From: dlmart2 [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 09, 2001 1:40 AM
> To: Chuck.Irvine; info-cvs
> Cc:
David L. Martin writes:
>
> Unix: Fri Jan 5 18:09:51 2001
> WinCVS: Fri Jan 05 18:09:51 2001
The C Standard clearly requires the space, not a zero, but it's easy
enough to check for, so I've added code to CVS to fixup the timestamp if
it's got a leading zero. (I don't know if that will help Wi
1:24 AM
Subject: Re: WinCVS incorrectly showing locally modified files
> David L. Martin writes:
> >
> > Unix: Fri Jan 5 18:09:51 2001
> > WinCVS: Fri Jan 05 18:09:51 2001
>
> The C Standard clearly requires the space, not a zero, but it's easy
> enough to check for
