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

Re: annotate vs blame

From: Gareth McCaughan <Gareth.McCaughan_at_pobox.com>
Date: 2002-08-30 10:45:00 CEST

On Thursday 29 August 2002 10:46 pm, Nicholas Riley wrote:

[Peter Davis suggested:]
> > svn trace path/to/file
> >
> > traces the file, which obviously (to me, anyway) means tracing
> > the origins of that file (and thus the origins of specific lines
> > within that file).

> Not to me, at all. How about something like 'svn activity' or 'svn
> happenings' or 'svn changes' or 'svn eventlog'? History is really
> the word you want to use here, but with the implication that you're
> picking out the particular path that leads to the target. If you
> were talking about people, 'svn ancestry' might be good.
> "Trace" by itself doesn't imply that, but perhaps something like
> 'svn tracehist' might... It's really much clearer if there's a
> verb involved. Even blame would be better as 'svn showblame'.

("Blame" is a verb as well as a noun.)

While we're in random-suggestions mode: I think all of the
following are at least defensible. review, audit, scrutinize,
inspect, slice, dig, stratify. (The image behind the last two
is of an archaeologist or a geologist digging into the ground
and revealing strata corresponding to different periods.)

By the way, another (usually more verbose) way to present
roughly the same information, which might have advantages
for some purposes, is as a series of diffs, one per revision
in which the file changed, each accompanied by the appropriate
log message. You can think of this either as a turbocharged
"svn diff" (showing diffs for intermediate revisions) or as a
turbocharged "svn log" (showing diffs as well as metadata).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 30 10:45:33 2002

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.