You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@subversion.apache.org by Dan Ellis <da...@gmail.com> on 2014/05/03 00:24:40 UTC

svnmucc and line endings

Hi,

svnmucc currently only supports linefeed (LF, \n) line endings and
complains about window's style carriage return, linefeed (CRLFs, \r\n) with:
Error: svnmucc: E125005: Cannot accept non-LF line endings in 'svn:log'
property

This is inconsistent with the svn command line that allows both but
requires consistency.  Is there any consideration of supporting both
styles?  Not supporting \r\n causes some scripting pain to clean up the
file to the single format.

Thanks,
Dan

Re: svnmucc and line endings

Posted by Dan Ellis <da...@gmail.com>.

Thank you very much for the speedy change!


On Fri, May 2, 2014 at 10:54 PM, Ben Reser <be...@reser.org> wrote:

> On 5/2/14, 3:24 PM, Dan Ellis wrote:
> > svnmucc currently only supports linefeed (LF, \n) line endings and
> complains
> > about window's style carriage return, linefeed (CRLFs, \r\n) with:
> > Error: svnmucc: E125005: Cannot accept non-LF line endings in 'svn:log'
> property
> >
> > This is inconsistent with the svn command line that allows both but
> requires
> > consistency.  Is there any consideration of supporting both styles?  Not
> > supporting \r\n causes some scripting pain to clean up the file to the
> single
> > format.
>
> Done on trunk in r1592148 and r1592150.
>
> For what it's worth it is also inconsistent with svnmucc since when
> SVN_EDITOR
> is called to retrieve the log message it handles line ending normalization.
>
> Thanks for the request.
>

Re: svnmucc and line endings

Posted by Ben Reser <be...@reser.org>.

On 5/2/14, 3:24 PM, Dan Ellis wrote:
> svnmucc currently only supports linefeed (LF, \n) line endings and complains
> about window's style carriage return, linefeed (CRLFs, \r\n) with:
> Error: svnmucc: E125005: Cannot accept non-LF line endings in 'svn:log' property
> 
> This is inconsistent with the svn command line that allows both but requires
> consistency.  Is there any consideration of supporting both styles?  Not
> supporting \r\n causes some scripting pain to clean up the file to the single
> format.

Done on trunk in r1592148 and r1592150.

For what it's worth it is also inconsistent with svnmucc since when SVN_EDITOR
is called to retrieve the log message it handles line ending normalization.

Thanks for the request.