On 6/12/07, Lübbe Onken <l.onken@rac.de> wrote:
> Hi Lasse,
>
> You wrote:
>
> > 1. Add the line-ending setting and accept that TSVN will sometimes
> > report a successful commit when it has only committed some of the
>
> As others already said, there seems to be a bug in the underlying SVN
> libraries, which leads to this behaviour. You should fix the inconsistent
> newlines in your working copy after adding and before committing the file.
I will fix my line endings and keep the property, however what is the
formal procedure for reporting this as a bug to TSVN or SVN so that it
can be fixed?
As far as I can tell, this is a rather serious issue, that the Commit
command will happily abort a commit, say "A-Ok" and not have done
everything it should.
> > 2. Not add the line-ending, and accept that some files have
> > inconsistent line endings
>
> This may lead to diff&merge programs failing on the file.
Upon reading in on this, it seems SVN will keep the files in an
internal state with only the LF characters in place, so I don't see
how other SVN programs would fail with this problem. However, when
doing a Get latest, I understand that unless I have this property the
file won't have the right line ending type on my system so the
software I use to maintain the files might not work.
> > how can
> > I detect that I even have the problem if TSVN will sometimes just bail
> > out and look happy as a pig about it?
>
> Fix the files before committing. TortoiseSVN complains about the
> inconsistent newlines the moment you add the files.
I will have to use the Add command consistently when adding new files
then. My own software will happily handle both line endings in this
respect in all the cases that this might occur, and since the Commit
command seems to be broken in this regard I will have to keep using
Add first.
--
Lasse Vågsæther Karlsen
mailto:lasse@vkarlsen.no
Received on Thu Jun 14 12:34:23 2007