Mail Archives: djgpp-workers/2000/12/16/04:36:56
> In addition, we could make the I/O mode be sensitive to the repository
> location: a remote repository is probably almost always a Unix box.
I'm not sure that would be a good idea. And besides, the Unixness of the
repository doesn't matter that much anyway - it's what's stored in it
that matters. If a Unix repository only has C sources, using text mode is
quite acceptable; if a DOS repository needs to keep Unix-style and
DOS-style text, it isn't.
> Things are not that bad: latest versions of GNU Patch have a --binary
> option which strips the CRs from the diffs, before applying them.
> Using --binary, I can apply on Unix diffs generated on a DOS machine,
> and it all works.
I know - but what if, say, you checked out the CVS sources (in text mode,
so you end up with all CRLF). You edit some files, including the
MSVC project files. You make a diff, which would either use text mode or
binary mode.
If it used text mode, the patches to the project files would fail (as
they're CRLF in the repository). And if binary mode was used, you'd be
introducing CRLFs into the Unix-style sources.
Unless I'm mistaken about how patch --binary operates, it would not help
in this case - you'd still have to know which files were CRLF originally
and make a separate diff for them.
- Raw text -