Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
On 9/2/06, Tony Hoyle <tony.hoyle at march-hare.com> wrote: > Yongwei Wu wrote: > > Is it not allowed to let *me* have UNIX line endings in Windows (like > > in UNIX), while other people still have the Windows line endings? > > > A file is either a text file (and needs line endings specific to the > platform it's running on - cr/lf for windows), a platform specific file > (marked with -kL, -kD or -kM) or is binary. An individual user forcing > unix line endings on windows for all files doesn't make any sense. > > Why do you think you need this? Why do people use Cygwin, UWin, and such like on Windows? Why do people on Windows need UNIX line endings at all? :-) -- It is simply the way people who are used to UNIX work when they have to work on Windows. For me, I often check out files on Windows from the SourceForge CVS server, and sometimes need to run/use them in Cygwin, or copy them around. It is much simpler if I check all files with UNIX line endings. Of course I should not force others to use UNIX line endings, let alone it is not possible in my case, since SF uses CVS instead of CVSNT. I can use Cygwin CVS too. However, unless I am forced away from CVSNT, I would like to take advantage of the extra CVSNT features, and make life easier to have only one CVS executable on my Windows box. Best regards, Yongwei -- Wu Yongwei URL: http://wyw.dcweb.cn/