On 2/4/06, D.J. Heap <djheap@gmail.com> wrote:
> On 12/23/05, D.J. Heap <djheap@gmail.com> wrote:
> [snip]
> >
> > I even tried changing the eol-style over a few revisions on a new
> > repository, but still couldn't make it fail. I wonder if the
> > Subversion repository has some mixed eol's in files that have been in
> > it forever or something like that? It works fine on Linux, though, so
> > probably not.
>
>
> I'm looking into this again, and blame seems to act unexpectedly on
> Windows when eol-style is changed. The author of the revision *after*
> the eol-style change gets credit for all lines.
>
> I might have expected that (eol change on every line), but the blame
> code seems to go to lengths to avoid that sort of thing, doesn't it?
>
Even worse, on Windows doing:
svn blame -r1:4657 build.conf
gives no errors, but outputs corrupt lines and not even all the lines.
Blaming r1:4656 at least gives consistent output and the whole
file...it looks like r4657 (a one line change to build.conf) causes it
to flip out. But it doesn't actually throw an error until blaming
r1:4805 -- after that blame never works for build.conf on Windows (or
probably any platform where native eol is not LF), it just throws the
'inconsistent eols' error.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 4 17:51:17 2006