Re: [Issue 2543] Inconsistent svn diff after rename

> On 5/10/06, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
>
> > Unless there are two radically different use cases that I've been
> missing,
>
> Yes, the two radically different use-cases for dealing with a file
> that is schedule-add-with-history are
>
> * "Show me exactly what's going to be sent into the repository."
>
> * "Show me my local edits."

Which are 2 wildly differing questions. Why did we conflate those into 1
command? I mean, the fact that they both use a diffing library and both
output unidiff can't be the reason: we didn't include switching
functionality into the update command.

> They are mutually exclusive behaviors, but both are legitimate things
> you may want to do with a schedule-add-with-history file. One
> behavior should be the default, and the other should be toggled by a
> switch. At the moment, the 2nd behavior is all we do.

Why not by a command? svn show-how-my-changes-affect-the-repository?

> You make a good argument that the 1st behavior should be the default,
> for the sake of consistency with other diff commands. If it's
> changed, please at least make the 2nd behavior still triggerable
> somehow.

Actually, I think 'diff' - when using svn as a drop-in replacement for CVS -
should address the 'what are my local changes' question. I'd argue that both
svnlook and repos->repos diff are both at fault here.

The question 'how did my changes affect the repository' can't be answered by
generating a unidiff. I'm actually sorry we even keep trying to do that
instead of figuring out how to write 'svn patch'.

bye,

Erik.

-- 
Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%!
Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org