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

Re: MT 'blame' and 'log' Auditing - Design Specification

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-04-28 19:38:23 CEST

On 4/28/07, Stefan Küng <tortoisesvn@gmail.com> wrote:
> Mark Phippard wrote:
> > I still do not agree with this part of the spec:
> >
> > svn blame
> > Two additional columns for each line, with the original revision
> > and author of that line. Unlike other commands, we do not need to
> > worry about multiple source revisions, because each line can have at
> > most one author.
> >
> >
> > I object to the two additional columns. If I run svn blame
> > --merge-sensitive I do not need to see any other information. I
> > thought at one point we even said that were it not for the expected
> > performance hit in getting the merge information that svn blame should
> > just always return this information. When using blame it is not
> > likely that someone would want any other information.
> >
> > The reason I object is just that all the GUI tools out there that
> > already work with blame output will be able to do so easier if a
> > command line option simply alters the data we get back as opposed to
> > giving us an all new format to deal with.
> I don't understand. Do you call the svn client from Subclipse and parse
> its output? I don't think you do it that way, so why bother with how the
> svn client will show the additional information? It shouldn't bother you
> how many columns there are since you would be using the blame callback
> which I think will simply have some more callback params to use.
> Or am I completely wrong here?

We use the blame callback API, but if this approach is taken then
presumably the API has to change too which means our implementation
does need to account for this. I would rather let the process that
runs blame API set the boolean correctly and let the output remain the

> "svn info, svn ls --verbose and svn status --show-updates are purposely
> not included in this list, on the grounds that one would typically need
> more information than they can reasonably provide. Adding more output to
> these commands would clutter their interface, further reducing their
> utility."
> I think here I disagree. I'm ok with this if you're only referring to
> the command line client. But the API should still provide that
> information if it's available. You don't know how other (UI) clients
> could make good use of such information. Always remember, an UI client
> isn't limited to 80 chars screen width.
> Especially the svn_client_status() function should return that
> information if it is available.

The issue is that these API's are setup to show single values. When
you are dealing with an entire file a commit from a merge could have
changes to the file from many revisions and authors. How are commands
like status, info and ls (even in a GUI) possibly going to deal with

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 28 19:38:42 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.