Re: cvs commit: logging-log4net/src/Util PatternString.cs
On Thu, 12 May 2005, Nicko Cadell <[EMAIL PROTECTED]> wrote: > I haven't played around with subversion too much and I don't know > how it deals with the LF / CRLF issue, I guess we will find out ;) Unlike CVS, Subversion treats all files as binary files - and doesn't do any keyword expansion either - unless you tell it to. You have to set properties on the individual files to make it translate line-feeds or make any other changes. For people working on Unix it is a bit annoying if you have cariage returns in the files and as soon as you have a committer working on Unix you may end up with files that have mixed line-ends since the code she/he added would have line-feeds only. Where it becomes a real problem is when you have Unix shell scripts in the module since the shell will see the cariage return in the she-bang line and fail with something like "file not found /bin/sh^M" where ^M is a \r and easy to overlook. Stefan
RE: cvs commit: logging-log4net/src/Util PatternString.cs
At my company we use cygwin to simulate a UNIX environment under Windows. It makes sense to do that using the cygwin UNIX mode. UNIX mode just means don't do anything clever. DOS mode means do this magic to convert a LF into a CRLF when reading and do the reverse when writing. In general I am not in favour of any sort of magic behaviour which hides the underlying data, or makes it difficult to work around. Because of my unix background I use the cvs command line client from the cygwin package, I find it faster to use than the various equivalent UIs that are available, but that's just me. I also like the UNIX tools and terminal window which I can just drag to resize etc. I haven't played around with subversion too much and I don't know how it deals with the LF / CRLF issue, I guess we will find out ;) Cheers, Nicko > -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 12 May 2005 11:57 > To: log4net-dev@logging.apache.org > Subject: Re: cvs commit: logging-log4net/src/Util PatternString.cs > > On Wed, 11 May 2005, Nicko Cadell <[EMAIL PROTECTED]> wrote: > > > I use cygwin cvs which is configured to work in UNIX mode > on my WinXP > > box. This is not really by design, its just the way it is right now. > > I don't want to make an issue of this, but I'm curious. Why > are you using the UNIX mode instead of DOS? Is there some > other tool that works better that way? Is it just "for > historic reasons"? > > Stefan >
Re: cvs commit: logging-log4net/src/Util PatternString.cs
On Wed, 11 May 2005, Nicko Cadell <[EMAIL PROTECTED]> wrote: > I use cygwin cvs which is configured to work in UNIX mode on my > WinXP box. This is not really by design, its just the way it is > right now. I don't want to make an issue of this, but I'm curious. Why are you using the UNIX mode instead of DOS? Is there some other tool that works better that way? Is it just "for historic reasons"? Stefan
RE: cvs commit: logging-log4net/src/Util PatternString.cs
I use cygwin cvs which is configured to work in UNIX mode on my WinXP box. This is not really by design, its just the way it is right now. There is a plan for the logging services project to migrate to subversion in the middle of this year. When that happens we will probably switch (pending a discussion on this list at the appropriate time) to DOS mode, i.e. where the client to translate the DOS line endings to UNIX ones before writing to the server. Nicko > -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 11 May 2005 14:35 > To: log4net-dev@logging.apache.org > Subject: Re: cvs commit: logging-log4net/src/Util PatternString.cs > > Nicko, > > I've seen that in several commit mails now. It seems the > sources have been copied from a Windows system to a Unix box > and committed from there. All files I've seen so far have > been checked in with Windows line-ends inside the file. Is > this intentional? > > I think somebody with CVS karma and access to a Unix box > should fix all line-ends (using dos2unix, tr or Ant's > task, for > example) and re-commit the files. > > Stefan >
Re: cvs commit: logging-log4net/src/Util PatternString.cs
Nicko, I've seen that in several commit mails now. It seems the sources have been copied from a Windows system to a Unix box and committed from there. All files I've seen so far have been checked in with Windows line-ends inside the file. Is this intentional? I think somebody with CVS karma and access to a Unix box should fix all line-ends (using dos2unix, tr or Ant's task, for example) and re-commit the files. Stefan
