If other subcommands are affected by this, I would propose that we
fix them all then. Not knowing whether an outputted path is a file or
directory can be a pain to find the answer to usually requiring a
server round trip. From a scripting perspective, this is problematic.
I agree with consistency so I understand that if agreed upon, my
patch would have to potentially touch many subcommands but in the end,
I think having a visible way to distinguish file path from directory
path would be a great update to Subversion's output.
On 10/15/07, Mark Phippard <email@example.com> wrote:
> On 10/15/07, Jeremy Whitlock <firstname.lastname@example.org> wrote:
> > Hi All,
> > When writing a script I recently ran across a situation that
> > caused me a good bit of heart ache. When you run "svn diff
> > --summarize" and you get the output, there is no way to distinguish
> > between files and directories. Here is an example:
> > $ svn diff --summarize
> > http://svn.collab.net/repos/svn/branches/ctypes-python-bindings
> > -r24577:HEAD
> > .....
> > A http://svn.collab.net/repos/svn/branches/ctypes-python-bindings/test
> > .....
> > There is no way to tell in a scripted/automatic fashion whether "test"
> > is a file or directory. I would like to propose that we make our
> > commands display visible differences between files and directories.
> > The way it would work is that all directories would end with a
> > trailing slash. This makes viewing the output and making a better
> > analysis more exact and it also gives script writers the ability to
> > distinguish between files and directories without having to do a
> > server round trip. The only way to do this now is with some sort of
> > server round trip and it shouldn't be necessary. What do you think?
> > If you are interested in seeing this in the core, I can submit a
> > patch.
> I know people have complained about this with log output as well. I
> am not sure why we stuck with current output, but I imagine diff
> --summarize is just being consistent.
> Mark Phippard
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Oct 15 19:06:01 2007