[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 17:21:54 CEST

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.


On 4/28/07, Hyrum K. Wright <hyrum_wright@mail.utexas.edu> wrote:
> Hash: SHA1
> With the merge tracking auditing functional spec pretty much fleshed
> out, we're going to start working on the API and design specification.
> Dan and I are going to visit in IRC on Monday at 12pm CDT (-0500), and
> anyone with an interest in this work is welcome to join. Afterward,
> I'll distill the relevant material and and post it to the list before
> anything is finalized.
> - -Hyrum
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> iD8DBQFGM2TICwOubk4kUXwRAgfBAKDHC2jVPKC7N2t6qmun7irEjzPOPwCeJF6i
> IW5jx4nfRucJB1uIumitjXg=
> =Z46e

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 17:24:09 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.