> I know there are a lot of people very rabidly against doing anything
> like this to CVS. However, the fact that it comes up so often
> indicates that it should be seriously considered. I know it's not
> something that should just be slapped in in a weekend, but it also
> shouldn't be completely condemned just because a 100% wonderful
> solution isn't immediately obvious.
I would not mind if CVS transmited and stored _text_ files with a
unique "standard" line-terminating convention. For example, like SMTP
(CRLF). While the various CVS clients write localy the file with the
local line-terminating convention. Like Eudora on Macintosh writes
messages with CR endings on Macintosh, while Eudora on MS-Windows
writes them with CRLF, and emacs on unix writes them with LF. (And I
suppose UAs in record based systems write them in records).
If it's so smoothly implemented for the mail system, I don't see what
difficulties there may be to implement it for CVS.
--
__Pascal Bourguignon__ PGP Key ID: 0xEF5E9966 (o_
mailto:[EMAIL PROTECTED] PGP fingerprint: 00 F5 7B DB CA 51 8A AD 04 5B //\
http://informatimago.free.fr/index 6C DE 32 60 16 8E EF 5E 99 66 V_/
() Join the ASCII ribbon campaign against html email and Microsoft attachments.
/\ Software patents are endangering the computer industry all around the world.
Join the LPF: http://lpf.ai.mit.edu/ http://petition.eurolinux.org/
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
