bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #22781] cvs update (1.11.22 on Windows) uploads excessive numbe


From: Mark D. Baushke
Subject: Re: [bug #22781] cvs update (1.11.22 on Windows) uploads excessive numbers of files after daylight saving time changes
Date: Mon, 31 Mar 2008 10:43:19 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nelson B Bolyard <INVALID.NOREPLY@gnu.org> writes:

> Follow-up Comment #4, bug #22781 (project cvs):
> 
> Thanks, Mark, for fixing those source files.  

Thank you for bringing the problem to our
attention.

> Before I submit another patch, I have a few
> questions:

Sure.

> 1) Would you prefer that I change my patch to
> use Unix line endings before submitting it?

Attaching the output of a 'cvs diff' to the bug
report should be sufficient. I am not going to
worry too much about line endings and can easliy
strip them if needed.

> 2) should my patch include changes to the ChangeLog files?

Well, we will need to rewrite the header to be one
of the real committers, but if you could provide
the text of the log entry, that would be much
appreciated.

> 3) My patch changes all the *.mak files (used by nmake), 
> but does not change any of the other make-related files 
> such as *.dsp, *.dsw, *.dep or the Makefile.{am.in} files 
> in Windows-NT.  Is that a problem?  Are those files actually
> used in your Windows builds?  

I am not able to answer this question. I do not
have the ability to do any of the Windows builds
myself as I do not have any system running Windows
nor do I have any 'compiler' or 'make' which would
run on a Windows platform unless it might be gcc
with Cygwin, but it is intended that the Windows
CVS client should not depend upon Cygwin.

Is anyone else able to answer Nelson's question?
Will we be able to generate a Windows binary for
use of CVS users after we accept his patch?

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFH8SK2Cg7APGsDnFERAnDpAJ9hinAkO+vpTo67W0nTMekQzRk3eACffuZA
y/+jc9CTSTK3UzEBPUNYnBY=
=oEiB
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]