You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "C. Michael Pilato" <cm...@collab.net> on 2008/09/23 14:33:02 UTC
Re: svn commit: propchange - r280 - svn:log
cmpilato@tigris.org wrote:
> Author: cmpilato
> Revision: 280
> Property Name: svn:log
> Action: modified
>
> Property diff:
> --- old property value
> +++ new property value
> @@ -1,112 +1,112 @@
[...]
My svnsync mirroring of our repository is erroring out because some of our
old log messages have non-LF-style line endings. These propchanges you see
are just line-ending corrections.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: svn commit: propchange - r280 - svn:log
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
C. Michael Pilato wrote on Tue, 23 Sep 2008 at 12:59 -0400:
> Lieven Govaerts wrote:
> > C. Michael Pilato wrote:
> >> My svnsync mirroring of our repository is erroring out because some of our
> >> old log messages have non-LF-style line endings. These propchanges you see
> >> are just line-ending corrections.
> >>
> >
> > I had the same problem last week, and wondered if we shouldn't make
> > svnsync raise a warning, but just put a 'fixed' log message in the
> > destination repository. Not everyone using svnsync has write access to
> > the source repo.
>
> I imagine that *somebody* has write access to most source repo's, though, in
> which case it would be a good idea for the readers of that repository to
> complain loudly about their invalid log message so they can fix the problem.
>
FWIW, similar considerations apply to the "FS doesn't accept non-UTF-8
filenames any more" fix (r33148), except that fixing the source repository
is harder (since the history has to be changed).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: propchange - r280 - svn:log
Posted by "C. Michael Pilato" <cm...@collab.net>.
Lieven Govaerts wrote:
> C. Michael Pilato wrote:
>> My svnsync mirroring of our repository is erroring out because some of our
>> old log messages have non-LF-style line endings. These propchanges you see
>> are just line-ending corrections.
>>
>
> I had the same problem last week, and wondered if we shouldn't make
> svnsync raise a warning, but just put a 'fixed' log message in the
> destination repository. Not everyone using svnsync has write access to
> the source repo.
I imagine that *somebody* has write access to most source repo's, though, in
which case it would be a good idea for the readers of that repository to
complain loudly about their invalid log message so they can fix the problem.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: svn commit: propchange - r280 - svn:log
Posted by Lieven Govaerts <sv...@mobsol.be>.
C. Michael Pilato wrote:
> cmpilato@tigris.org wrote:
>> Author: cmpilato
>> Revision: 280
>> Property Name: svn:log
>> Action: modified
>>
>> Property diff:
>> --- old property value
>> +++ new property value
>> @@ -1,112 +1,112 @@
>
> [...]
>
> My svnsync mirroring of our repository is erroring out because some of our
> old log messages have non-LF-style line endings. These propchanges you see
> are just line-ending corrections.
>
I had the same problem last week, and wondered if we shouldn't make
svnsync raise a warning, but just put a 'fixed' log message in the
destination repository. Not everyone using svnsync has write access to
the source repo.
Lieven
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org