You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Oliver Dain <od...@ll.mit.edu> on 2003/08/08 22:18:11 UTC
Using an external diff program with Subversion
I want to use a GUI diff program I have with subversion, so I changed
the subversion config file to point to this program (exam-diff).
Subversion now launches the program as expected, but the program didn't
understand the arguments subversion passed to it. I wrote a 3 line C
program that simply outputs all of the arguments passed to it so I could
see what Subversion was passing to my diff program:
c:>svn diff --diff-cmd "foo.exe" Engine.vcproj
Index: Engine.vcproj
===================================================================
foo.exe
-u
-L
Engine.vcproj (revision 295)
-L
Engine.vcproj (working copy)
.svn/text-base/Engine.vcproj.svn-base
Engine.vcproj
As you can see it passed a -u, 2 -L flags, some names for these files
and THEN the 2 files to be compared. That doesn't work with exam-diff.
It simply wants the names of the 2 files to be compared. How do I get
Subversion to pass just those last 2 command line args (the file
names)? If I try to use the -x option to svn diff passing blanks or
other arguments it passes those arguments AND all the stuff above:
c:> svn diff --diff-cmd "foo.exe" -x "a b" Engine.vcproj
Index: Engine.vcproj
===================================================================
foo.exe
a
b
-L
Engine.vcproj (revision 295)
-L
Engine.vcproj (working copy)
svn/text-base/Engine.vcproj.svn-base
Engine.vcproj
Any help appreciated (this should probably be documented in the manual
somewhere. I could't find it anywhere...)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Greg Thomas <Gr...@TheThomasHome.co.uk>.
On Tue, 12 Aug 2003 22:22:01 +0100, you wrote:
> Create a wrapper ".../diff-wrappers/gnudiff"
...
> Anyway, is it possible to write an equivalent DOS batch file?
Yup.
REM Clear the diff argument list
set ARGS=
REM Default diff argument if there are only four parameters
if "%5" == "" SET ARGS=-u
:GETNEXTARG
REM If we've only four arguments left, do the diff
if "%5" == "" goto DODIFF
REM Add the first argument to the wrapper to the diff arguments
set ARGS=%ARGS% %1
REM Shift the arguments along by one
shift
REM Go around again for the next argument
goto GETNEXTARG
:DODIFF
diff %ARGS% -L "%1" -L "%2" "%3" "%4"
REM Clear the argument list
set ARGS=
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Greg Hudson <gh...@MIT.EDU>.
On Tue, 2003-08-12 at 18:46, Philip Martin wrote:
> > [It would be nice if one could specify something like:]
> >> diff-cmd = /path/to/diff/program %f1 %f2 -L %N1 -L %N2
>
> I don't think that will work. The external diff command isn't a
> single string, it's a program name and a list of arguments.
APR gives us apr_tokenize_to_argv(), which provides quoting semantics
similar to Unix shells (but without $foo or `foo` substitution, of
course). ra_svn uses it.
It's the % substitutions which get tricky. We could go over the result
of apr_tokenize_to_argv() and perform the % substitutions, but you
really want to do them at the same time to get sane quoting semantics.
I would think that "%f1" (with the quotes) should produce an
unsubstituted %f1, for instance, but the information that there were
quotes there is lost by the time we'd look at it.
(That's primarily why ra_svn tunnel agent commands don't let you
substitute in a username or portname or anything, right now.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Philip Martin <ph...@codematters.co.uk>.
Julian Foad <ju...@btopenworld.com> writes:
> [It would be nice if one could specify something like:]
>> diff-cmd = /path/to/diff/program %f1 %f2 -L %N1 -L %N2
I don't think that will work. The external diff command isn't a
single string, it's a program name and a list of arguments. To
implement the above idea Subversion would be required to parse the
line into program and arguments, which could be tricky if the program
name includes spaces (as tends to happen on Windows). We had similar
problems with SVN_EDITOR, asking Windows users to escape or quote
spaces was deemed unacceptable.
I think you would need to provide something like
diff-cmd = /path/to/program
diff-cmd-arg1 = %f1
diff-cmd-arg2 = %f1
diff-cmd-arg3 = -L%N1
diff-cmd-arg4 = -L%N2
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Julian Foad <ju...@btopenworld.com>.
[Moved from "users" to "dev" list.]
Making it Easier to Use Non-GNU Diff Programs
The big picture:
People need to use programs other than the built-in diff or GNU diff, for reasons such as showing differences in a gzipped text file (zdiff), showing differences while still highlighting syntax (vimdiff), showing differences in a more graphical user interface, showing differences other than on a line-by-line basis, etc.
First we want to be able to invoke any external diff program easily. At the moment it is possible to invoke any external diff program, by using a wrapper, but a bit awkward and inconsistent. This treatise is essentially about making it easier.
Then, at some time in the future, we want Subversion to select different diff programs for different types of file, so that you can diff a whole tree and get sensible output for all types of file. I am not discussing that here, but I like to bear it in mind.
Do we need to think about whether the output of a given "diff" program could be used for "patch" or "merge" purposes? No; that is an interesting subject for the far future but for the medium term we just want to see the differences.
Wrapper scripts versus built-in syntax:
Much discussion has explicitly or implicitly argued for wrapper scripts or built-in syntax against the other method. But a wrapper can always be used, so the questions should be:
- Is it worth improving the wrapper-script interface?
- Is it worth ALSO having a built-in way to invoke various diff executables directly?
I hope I don't misrepresent anyone's meaning when I paraphrase from the "users" list thread "Using an external diff program with Subversion"...
Oliver Dain said (and others have said before):
[It is awkward to use non-GNU diff programs with the "--diff-cmd" option.]
[It would be nice if one could specify something like:]
> diff-cmd = /path/to/diff/program %f1 %f2 -L %N1 -L %N2
Sander Striker wrote:
> We can't go and support all diff programs out there. We currently
> use diff compatible cmdline arguments. If you want to use a different
> tool you need a wrapper to extract the arguments and pass those to
> 'exam-diff'.
Robert Spier wrote:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1390
> http://subversion.tigris.org/issues/show_bug.cgi?id=1388
>
> The discussion tapered off -- but there was no consensus as to whether
> to go with options or a wrapper script.
and
[If you use multiple diff programs, you want multiple configurations in the config file so that you don't have to specify the format of their basic options on the command line every time. E.g.:
diff-cmd[gnu] = diff -u -L %N1 -L %N2 %f1 %f2
diff-cmd[xxdiff] = xxdiff %f1 %f2
]
That's a very good point which I have not seen raised before. The ability to specify the options for multiple diff commands in the config file could be very nice, but it seems like quite a lot of work to design and implement (which I think was what you implied).
> That's the real catch for replaceable parameters -- because you don't
> want to specify them on the command line.
You don't want to have to specify them on the command line all the time, but it would be better to be able to do it than not to be able to do it. Sensible defaults would help, such as: if the user doesn't specify where to put the labels, then they are not passed; if the user doesn't specify where to put the file names, then they are passed at the end of the command line. Then you could write:
svn diff --diff-cmd=xxdiff ... # xxdiff would just work
svn diff --diff-cmd=diff ... # GNU diff would work, but without nice labels
svn diff --diff-cmd=diff -x "-L %N1 -L %N2" ... # GNU diff would work with nice labels
What we need is a bit of design to see how one mechanism or the other might work. I have made some notes below on improving the support for wrapper scripts. It would be good if someone would make a similar proposal for replaceable parameters, considering the awkward things like how to handle paths that contain spaces.
Notes on changes to facilitate the use of wrapper scripts:
It is possible to use a wrapper script to run any diff program at the moment, but the operation of "--diff-cmd" is a bit ugly and is designed for and strongly biased towards GNU diff. I believe that it should become general (not GNU-specific).
The present mechanism for directly invoking an executable doesn't work even for GNU diff in all cases - e.g. a pathname beginning with a hyphen is interpreted as option flags; it needs a "--" ("end of options" marker) before the file name arguments.
(1) It passes "-u" by default if the user specifies no other options. It should pass no options if the user specifies no options. Presently the wrapper cannot determine whether the user specified no -x option or "-x -u".
(2) It passes "-L" before each label, so the wrapper has to extract the "-L" and the label and discard them or change the option to something appropriate. It should just pass the two labels and the two paths to the wrapper. (Also note that the "-L" option is not documented in diffutils-2.8.1; only the equivalent long option "--label" is documented.)
(3) To allow the --diff-cmd argument to be brief ("diff" rather than "/usr/bin/diff"), svn searches for it in the PATH, which is a useful recent enhancement. But svn diff wrappers probably don't belong in the global PATH, so it may be better to have it look in some svn-specific diff command path instead. This could be specified in the config file: e.g. "diff-wrappers-path = .../tools/client-side/diff-wrappers/". We should aim to include working wrappers for a few common diff programs in the default distributions of Subversion.
(4) How do we make wrappers that are portable between different operating systems? I suppose each particular "diff" command tends to exist on only one platform, so we don't need portable wrappers. But can you even write a Windows/DOS batch file that gets argument quoting etc. right (see example below)?
Let's say we change (1) and (2) and (3) in the ways I suggest above, and define the invocation syntax as:
diff-wrapper [ARG...] LABEL1 LABEL2 FILE1 FILE2
where ARGs are the extra arguments specified by "-x" or "--extensions". Then it is no longer specific to GNU diff. To use GNU diff we could do this to duplicate the existing behaviour:
Add "diff-wrappers-path = .../diff-wrappers/" into "~/.subversion/config".
Create a wrapper ".../diff-wrappers/gnudiff" containing:
#!/bin/bash
if [ $# = 4 ]; then
diff -u -L "$1" -L "$2" "$3" "$4"
else
ARGS=("$@") # creates an array variable
LABEL1="${ARGS[$(($#-4))]}"; unset ARGS[$(($#-4))]
LABEL2="${ARGS[$(($#-3))]}"; unset ARGS[$(($#-3))]
FILE1="${ARGS[$(($#-2))]}"; unset ARGS[$(($#-2))]
FILE2="${ARGS[$(($#-1))]}"; unset ARGS[$(($#-1))]
diff "${ARGS[@]}" -L "$LABEL1" -L "$LABEL2" "$FILE1" "$FILE2"
fi
Invoke it as:
svn diff --diff-cmd=gnudiff ...
svn diff --diff-cmd=gnudiff --extensions="-u -b" ...
etc.
Note that that is not as simple as you might expect it to be. Perhaps I missed a trick. It would have been a bit simpler if we had defined the user options to come after the four label and filename arguments. It's kind of cheating to change the specification to facilitate a particular implementation, but if it facilitates most implementations then it would be worth it. Anyway, is it possible to write an equivalent DOS batch file?
Note also that this example defaults to -u if no options are specified, because that is the current behaviour of --diff-cmd. But that is not a clean and important feature of "svn diff"; rather it is like saying "I want to use a different variation of GNU diff, one which defaults to Unified output." That part of the behaviour needs to be implemented as a wrapper, and if one is using a wrapper for that sort of reason, one might as well do the other argument processing in the wrapper too. But in many cases, replaceable parameters would do the job well without using a wrapper.
My summary:
- Replaceable parameters are usually easier to set up.
- Wrappers are more powerful (flexible).
- Use of wrappers requires less work on Subversion itself; indeed it is already possible.
- The present implementation essentially _requires_ a wrapper except with GNU diff.
- Therefore we should make it work well with wrappers, and/or make it work well with replaceable parameters.
- We should make the common cases simple to use. Most diff programs only need the two file names; it seems unreasonable to require a wrapper for those.
If we make changes (1) and (2) and maybe (3) above without implementing replaceable parameters, then a wrapper will be necessary in all known cases including GNU diff. That would even out the playing field. Would that be acceptable? (Provocative question! Anticipating some resistance, but the rules of the game allow only fair and logical objections. :-)
Actually, I would feel uncomfortable about doing that without first adding enough support for replaceable parameters to allow GNU diff to be used directly, with labels. But is that a fair and logical discomfort?
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Oliver Dain <od...@ll.mit.edu>.
>
>
>I don't see what the win is for replaceable parameters if you're going
>to have to use a wrapper script anyway.
>
>In my personal use case...
>
> most of the time I will use SVN's internal diff, or an external
> GNU diff.
>
> when doing comparisons, I might use xxdiff
>
> and maybe pdiff to print things.
>
>simplifying that, I've got GNU diff and xxdiff, which take very
>different argument flags.
>
>How would that work in the config file?
>
>diff-cmd[gnu] = ...
>diff-cmd[xxdiff] = ...
>
>?
>
>That's the real catch for replaceable parameters -- because you don't
>want to specify them on the command line. (Although a wrapper script
>on the outside... would fix that.)
>
>-R
>
>
I imagine a single diff-cmd line in the config file. In your case it
sounds like a wrapper is necessary so your config would look like:
diff-cmd = your/wrapper/pgm %f1 %f2 etc.
and then you'd use your wrapper like you are now. That's not any harder
than what you're doing now. In fact you might decide not to write a
wrapper and invoke svn diff like
svn diff --diff-cmd "/your/diff/pgm %f1 %f2"
allowing you to invoke all your favorite differs right from the command
line without a wrapper.
However, people like me who use a single diff program for all their diff
needs (I suspect these are the majority) would not have to write a
wrapper script and would have a diff-cmd like:
diff-cmd = /my/favorite/diff %f1 %f2
And we'd be done. If we later decided that for some strange reason we'd
like to use a different diff program for a single comparison (e.g. send
both files to emacs to edit instead of diffing) we wouldn't have to
write a wrapper or change the config file but could instead simply use
the --diff-cmd switch for this one exceptional case.
Thus the advantages are:
1) Its easier for users who want to invoke a single diff program
most/all of the time
2) Its not any harder for people currently using a wrapper
3) It allows you to invoke a funky diff program from the command line
without needing a wrapper or having to change your config file and also
makes the -x switch obsolete since you can pass all flags in any order
to your program right from the --diff-cmd switch.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Robert Spier <rs...@pobox.com>.
> I think replaceable parameters are much nicer than requiring a wrapper
> script. Its easier to set up but still allows you to use a wrapper if
> you want to do something really funky. For example, at my site I set up
> a wrapper to call my diff program of choice. A college liked my
> solution and wanted to use it but it had to be set up quite differently
> on his machine as paths, etc. were different in his environment. If I
> had been able to do it with just replaceable parameters it would have
> taken me less time to do and he would have been able to simply copy my
> cofig file and be up and running.
I don't see what the win is for replaceable parameters if you're going
to have to use a wrapper script anyway.
In my personal use case...
most of the time I will use SVN's internal diff, or an external
GNU diff.
when doing comparisons, I might use xxdiff
and maybe pdiff to print things.
simplifying that, I've got GNU diff and xxdiff, which take very
different argument flags.
How would that work in the config file?
diff-cmd[gnu] = ...
diff-cmd[xxdiff] = ...
?
That's the real catch for replaceable parameters -- because you don't
want to specify them on the command line. (Although a wrapper script
on the outside... would fix that.)
-R
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Oliver Dain <od...@ll.mit.edu>.
Thanks for the reply. Its not entirely clear what the status of the 2
proposed patches mentioned in your email are. One looks like it
requires you to pass all options via -x which, in my opinion, seems less
useful than replaceable parameters.
I think replaceable parameters are much nicer than requiring a wrapper
script. Its easier to set up but still allows you to use a wrapper if
you want to do something really funky. For example, at my site I set up
a wrapper to call my diff program of choice. A college liked my
solution and wanted to use it but it had to be set up quite differently
on his machine as paths, etc. were different in his environment. If I
had been able to do it with just replaceable parameters it would have
taken me less time to do and he would have been able to simply copy my
cofig file and be up and running.
Robert Spier wrote:
>There is a ticket open for this issue. Or two.
>
> #1390
> http://subversion.tigris.org/issues/show_bug.cgi?id=1390
> #1388
> http://subversion.tigris.org/issues/show_bug.cgi?id=1388
>
>The discussion tapered off -- but there was no consensus as to whether
>to go with options or a wrapper script. I think wrapper scripts are
>probably a better idea, because you may want to use multiple diff
>programs.
>
>
>At 09 Aug 2003 10:34:30 -0400,
>Oliver Dain wrote:
>
>
>>Thanks to all for the replies. I certainly could (and will) do the
>>wrapper thing. I'd think it'd be a nice feature if, in the config, one
>>could specify something like:
>>
>>diff-cmd = /path/to/diff/program %f1 %f2 -L %N1 -L %N2
>>
>>where the %x's get expanded to something useful (like %f1 = first
>>filename, %f2 = 2nd file name, %N1 = nice name of file one (the name
>>with the revision number), etc. That way you could easily support ALL
>>diff programs and users wouldn't have to write custom wrappers for each
>>diff program they want to use. Has anybody else suggested this?
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Robert Spier <rs...@pobox.com>.
There is a ticket open for this issue. Or two.
#1390
http://subversion.tigris.org/issues/show_bug.cgi?id=1390
#1388
http://subversion.tigris.org/issues/show_bug.cgi?id=1388
The discussion tapered off -- but there was no consensus as to whether
to go with options or a wrapper script. I think wrapper scripts are
probably a better idea, because you may want to use multiple diff
programs.
At 09 Aug 2003 10:34:30 -0400,
Oliver Dain wrote:
>
> Thanks to all for the replies. I certainly could (and will) do the
> wrapper thing. I'd think it'd be a nice feature if, in the config, one
> could specify something like:
>
> diff-cmd = /path/to/diff/program %f1 %f2 -L %N1 -L %N2
>
> where the %x's get expanded to something useful (like %f1 = first
> filename, %f2 = 2nd file name, %N1 = nice name of file one (the name
> with the revision number), etc. That way you could easily support ALL
> diff programs and users wouldn't have to write custom wrappers for each
> diff program they want to use. Has anybody else suggested this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Julian Foad <ju...@btopenworld.com>.
Oliver Dain wrote:
> Thanks to all for the replies. I certainly could (and will) do the
> wrapper thing. I'd think it'd be a nice feature if, in the config, one
> could specify something like:
>
> diff-cmd = /path/to/diff/program %f1 %f2 -L %N1 -L %N2
>
> where the %x's get expanded to something useful (like %f1 = first
> filename, %f2 = 2nd file name, %N1 = nice name of file one (the name
> with the revision number), etc. That way you could easily support ALL
> diff programs and users wouldn't have to write custom wrappers for each
> diff program they want to use. Has anybody else suggested this?
Yes, and other ways to achieve the same end ... but it hasn't been done yet.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Oliver Dain <od...@ll.mit.edu>.
Thanks to all for the replies. I certainly could (and will) do the
wrapper thing. I'd think it'd be a nice feature if, in the config, one
could specify something like:
diff-cmd = /path/to/diff/program %f1 %f2 -L %N1 -L %N2
where the %x's get expanded to something useful (like %f1 = first
filename, %f2 = 2nd file name, %N1 = nice name of file one (the name
with the revision number), etc. That way you could easily support ALL
diff programs and users wouldn't have to write custom wrappers for each
diff program they want to use. Has anybody else suggested this?
Thanks again,
Oliver
On Sat, 2003-08-09 at 10:19, Michael Wood wrote:
> On Fri, Aug 08, 2003 at 10:59:50PM -0600, Bruce Elrick wrote:
> [snip]
> > How about: Oliver modifies his 3-line C program into a wrapper that
> > discards all the arguments but the two file names and calls exam-diff?
> [snip]
>
> That's exactly what Sander means by a wrapper :) Although a batch file
> or shell script might also do.
>
> --
> Michael Wood <mw...@its.uct.ac.za>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Michael Wood <mw...@its.uct.ac.za>.
On Fri, Aug 08, 2003 at 10:59:50PM -0600, Bruce Elrick wrote:
[snip]
> How about: Oliver modifies his 3-line C program into a wrapper that
> discards all the arguments but the two file names and calls exam-diff?
[snip]
That's exactly what Sander means by a wrapper :) Although a batch file
or shell script might also do.
--
Michael Wood <mw...@its.uct.ac.za>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using an external diff program with Subversion
Posted by Bruce Elrick <br...@entropyreduction.ca>.
Sander Striker wrote:
>>From: Oliver Dain [mailto:odain@ll.mit.edu]
>>Sent: Saturday, August 09, 2003 12:18 AM
>
>
>>I want to use a GUI diff program I have with subversion, so I changed
>>the subversion config file to point to this program (exam-diff).
>>Subversion now launches the program as expected, but the program didn't
>>understand the arguments subversion passed to it. I wrote a 3 line C
>>program that simply outputs all of the arguments passed to it so I could
>>see what Subversion was passing to my diff program:
[...]
>
>>It simply wants the names of the 2 files to be compared. How do I get
>>Subversion to pass just those last 2 command line args (the file
>>names)?
>
>
> You don't. There is no such option.
How about: Oliver modifies his 3-line C program into a wrapper that
discards all the arguments but the two file names and calls exam-diff?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Using an external diff program with Subversion
Posted by Sander Striker <st...@apache.org>.
> From: Oliver Dain [mailto:odain@ll.mit.edu]
> Sent: Saturday, August 09, 2003 12:18 AM
> I want to use a GUI diff program I have with subversion, so I changed
> the subversion config file to point to this program (exam-diff).
> Subversion now launches the program as expected, but the program didn't
> understand the arguments subversion passed to it. I wrote a 3 line C
> program that simply outputs all of the arguments passed to it so I could
> see what Subversion was passing to my diff program:
[...]
We could have told you that. Or you could have found it in the source.
> As you can see it passed a -u, 2 -L flags, some names for these files
> and THEN the 2 files to be compared. That doesn't work with exam-diff.
We can't go and support all diff programs out there. We currently
use diff compatible cmdline arguments. If you want to use a different
tool you need a wrapper to extract the arguments and pass those to
'exam-diff'.
> It simply wants the names of the 2 files to be compared. How do I get
> Subversion to pass just those last 2 command line args (the file
> names)?
You don't. There is no such option.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org