Sheldon Gill <[EMAIL PROTECTED]> writes:
> Derek Zhou wrote:
> > Most sane Unix editors can cope with windows CR/LF automatically too;
> > as long as no one is mixing styles in the same file, everyone should be
> > fine. If the style is mixed up within the same file, even "eol-native"
> > can not
Derek Zhou wrote:
Most sane Unix editors can cope with windows CR/LF automatically too;
as long as no one is mixing styles in the same file, everyone should be
fine. If the style is mixed up within the same file, even "eol-native"
can not guranty to do the right thing anyway. My suggestion is the
Jeremy Bettis <[EMAIL PROTECTED]> writes:
> Derek Zhou wrote:
> > Yes, remove them all! All sane editors under windows can cope with unix
> > style LF automatically anyway. I don't think anybody here is using
> > notepad or vc.net, right? Derek
> >
> >
> I disagree. The svn:eol-native property i
On 9 Feb 2006, at 14:38, Jeremy Bettis wrote:
Derek Zhou wrote:
Andrew Ruder <[EMAIL PROTECTED]> writes:
Yes. The svn:eol-native property needs to be removed from the
files. I can do this, but I am curious which data files it is
messing up? But if none of the files need this property (I wa
On 08 Feb 2006 14:47:32 -0800, Derek Zhou <[EMAIL PROTECTED]> wrote:
> Yes, remove them all! All sane editors under windows can cope with unix
> style LF automatically anyway. I don't think anybody here is using
> notepad or vc.net, right?
Will removing all of these hurt anyone? I've got a list o
Derek Zhou wrote:
Andrew Ruder <[EMAIL PROTECTED]> writes:
Yes. The svn:eol-native property needs to be removed from the files. I
can do this, but I am curious which data files it is messing up? But
if none of the files need this property (I was under the impression it
was sta
Andrew Ruder <[EMAIL PROTECTED]> writes:
> Yes. The svn:eol-native property needs to be removed from the files. I
> can do this, but I am curious which data files it is messing up? But
> if none of the files need this property (I was under the impression it
> was standard operation with CVS),
On 8 Feb 2006, at 13:14, Andrew Ruder wrote:
On Wed, Feb 08, 2006 at 12:41:43PM +, Richard Frith-Macdonald
wrote:
Mostly this is just a bit annoying (you get a '^M' showing at the end
of each line when editing source code in vi), but it screws up data
files so they don't work. Any idea h
On Wed, Feb 08, 2006 at 01:43:16PM +, Richard Frith-Macdonald wrote:
> My understanding of the svn docs is that individual users can specify
> (based on file extension) default rules about which files use
> 'native' line termination if no property is specified in the
> respository. If th
On Wed, Feb 08, 2006 at 12:41:43PM +, Richard Frith-Macdonald wrote:
> Mostly this is just a bit annoying (you get a '^M' showing at the end
> of each line when editing source code in vi), but it screws up data
> files so they don't work. Any idea how to fix this?
Yes. The svn:eol-native
10 matches
Mail list logo