On Mon, 13 Dec 2004 kfogel@collab.net wrote:
> Eric Hanchrow <offby1@blarg.net> writes:
> > Find a text file whose svn:eol-style is native.
> >
> > $ file BUGS
> > BUGS: ASCII English text
> > $ svn pg svn:eol-style BUGS
> > native
> >
> > Edit the file by adding carriage-returns to the ends of the lines.
> > $ unix2dos BUGS
> > $ file BUGS
> > BUGS: ASCII English text, with CRLF line terminators
> >
> > Ask subversion if this file has changed.
> > $ svn st BUGS
> > $
> >
> > Hmm. Subversion says this file hasn't been edited, but of course it
> > has. This seems bugaceous (that's a word because I say it is :-); I
> > would have expected ``svn st BUGS'' to have yielded
> >
> > M BUGS
> >
> > Here's why it would be good to know that the file has been edited: if
> > the file in question were a Perl script instead of a text file, then
> > accidentally running ``unix2dos'' on it will break it (because the
> > kernel will look for an executable named /usr/bin/perl^M), and it
> > would be nice to be alerted to such breakage.
>
> So, thoughts folks? :-)
>
> I'm loathe to report a file as 'M'odified, if Subversion's not going
> to commit it when you type 'svn ci'. On the other hand, the working
> file *is* modified.
>
I think the current behaviour is logical. I think it is changes to the
"normalized" file that counts. Same for modifications inside an expanded
keyword, I think.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 13 22:56:34 2004