In article <[EMAIL PROTECTED]>, Stephan Feder wrote: >Kaz Kylheku wrote: >> >> In article <[EMAIL PROTECTED]>, Stephan Feder wrote: >> >Larry, >> > >> >I know how the cvs client handles line endings but nonetheless it is a >> >problem for quite a few users. What about a flag for the client that >> >prevents it from doing _any_ line ending conversions (as I understand it >> >the server transfers the files as they are)? >> >> You misunderstand. The problem is that some idiots took DOS text files >> sitting on a Linux client, and imported or added them to CVS. > >That means everyone with a working directory shared between windows and >unix boxes (not shared between multiple users!) is an idiot?
A resounding yes! This is lunacy, and moreover CVS does not support it. Do you >really think having two working directories with the same (apart from >line endings) checked out revisions is clever? No, only that it's the right thing that is properly supported by the software. >And if you (have to) >switch between systems while editing a file you have to check in system >1's file and update system 2's file. Yes, so what? >And you have to back it up. Backing up the repository after every single commit is not something that will scale well to a large repository with many users. >And >just maybe the proper line ending for editing is not the proper line >ending for processing. All of the tools on a given platform should agree about what the representation of a text file is. There are exceptions; for example Cygwin can be installed so that it uses Unix file representations. But then, arguably, Cygwin is a platform. Within that platform, the tools, including CVS, agree about what a text file is. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
