[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RFC -- Configurable Diff Path

From: Jeremy Whitlock <jcscoobyrs_at_gmail.com>
Date: 2007-07-17 00:50:29 CEST

Hi All,
    While working on issue 2723, which will update the core diff API
to have a method argument to specify the format (absolute or relative)
of the Index path output, has brought up conversation about having the
"svn diff" subcommand support an argument to override the default
handling of the Index path output. As of now, here are the tested
scenarios:

Scenario 1
---------------
svn diff RELATIVE_PATH_TO_WC (Outputs RELATIVE_PATH_TO_WC/MODIFIED_PATH)

Scenario 2
---------------
svn diff ABSOLUTE_PATH_TO_WC (Outputs ABSOLUTE_PATH_TO_WC/MODIFIED_PATH)

Scenario 3
---------------
svn diff -rOLD:NEW URL_TO_PATH (Outputs
PATH_RELATIVE_TO_REPO_ROOT/MODIFIED_PATH)

Now...why does this matter? Well, all of these scenarios end up with
the Index path not being -p0 compliant, which is the standard for most
project patches. (I understand you can run scenario 1 and scenario 3
in at least one way and end up with a -p0 compliant Index path but it
is not always guaranteed.) This being said, we started discussing
taking the work of issue 2723 and extending the Subversion command
line to support the passing of an argument to specify exactly how you
wanted your Index path output. Since this is still in the discussion
phase, I thought it would make sense to mention this on the list.

My personal suggestion would be to stick with the default handling as
it is but update all relative paths output to be relative to the
working copy root. (No need to modify the handling of scenario 3
since it already works as I would expect.) I would then have a
command line option to be able to specify absolute or relative for all
scenarios above which would override the default handling. (This
would not be used in scenario 3 where you use a URL for the path.)

What do you think? For those talking about this online with me, is
this inline with what we discussed? Feel free to discuss this by
responding to this thread so that when we have this taken care of, I
can use this thread as a reference.

Take care,

Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 17 00:49:43 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.