Re: [PATCH] optionally disable normalization of working copy files in diff invocations

2014-07-18 Thread Matthias Gerstner
> I'd hope we could address this without public API changes and > without adding yet another command line option. Yes the API change is pretty tough. > How about we make this the default if a third party diff tool is used? > This way, third party diff tools will always display differences in > ke

Re: [PATCH] optionally disable normalization of working copy files in diff invocations

2014-07-18 Thread Matthias Gerstner
Hi Julian, > A better interface, the user would tell Subversion what they really want: > >   svn diff --load-my-actual-file-not-a-copy-of-it >     # and I learnt that I won't have normalization in this case > > See the difference? I agree, that's more generic. > Then the question is, is it use

Re: [PATCH] optionally disable normalization of working copy files in diff invocations

2014-07-18 Thread Stefan Sperling
On Fri, Jul 18, 2014 at 11:32:57AM +0200, Matthias Gerstner wrote: > Having the configuration file options is sensible. I still find having > the explicit command line variant useful as most (or all?) other diff > related options are also there. This duplication exists for historical reasons, but

--strict vs --no-newline

2014-07-18 Thread Julian Foad
Julian Foad wrote on 2014-06-17: > [We had] >>   * svnversion --no-newline >> >>   * svn propget --strict # basically means no-newline > >    * svnlook youngest > >    * svn youngest --no-newline    # subcommand added after 1.8 > > and I just added a --no-newline option to 'svnlook youn

Don't release 'svn youngest'? [was: --strict vs --no-newline]

2014-07-18 Thread Julian Foad
Do we really want to release in 1.9 the 'svn youngest' command that was introduced recently? There are several kinds of 'youngest' rev we might want to ask for, and we already have the following ways of asking for several of them:   svn info URL | grep 'Revision:'     # head rev of repo   svn