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

Re: Auditing Design - v1

From: Stefan Haller <haller_at_ableton.com>
Date: 2007-03-06 09:01:59 CET

Hyrum K. Wright <hyrum_wright@mail.utexas.edu> wrote:

> This idea of representing the merged revisions inline when using
> '--merge-sensitive' is starting to grow on me. Should they be included
> in all 'svn log' invocations, or just enabled by using '--verbose'?

No, '--verbose' would be the wrong flag for this. '--merge-sensitive'
should control whether the merged revisions show up at all; and if they
do, '--verbose' should control whether the changed path information is
shown for them, like for every log entry.

> I guess, without '--verbose' it may be difficult to determine that the
> revision came in as a result of a merge.

I'm strongly in favour of indenting the log entries for the merged
sub-revisions (with a new level of indentation for every merged revision
that was in turn a merge). This is particularly important with
--merge-sensitive and --quiet, but without --verbose:

------------------------------------------------------------------------
r23493 | malcolm | 2007-02-24 09:24:26 +0100 (Sat, 24 Feb 2007)
------------------------------------------------------------------------
r23474 | dlr | 2007-02-23 00:04:33 +0100 (Fri, 23 Feb 2007)
  ----------------------------------------------------------------------
  r23406 | blair | 2007-02-16 03:30:50 +0100 (Fri, 16 Feb 2007)
  ----------------------------------------------------------------------
  r23405 | blair | 2007-02-16 03:29:38 +0100 (Fri, 16 Feb 2007)
------------------------------------------------------------------------

-- 
Stefan Haller
Ableton
http://www.ableton.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 6 09:02:22 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.