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

Re: [PATCH] 'svn blame --xml' - v5

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-05-09 21:30:30 CEST

On Mon, 9 May 2005 kfogel@collab.net wrote:

> Øyvind A. Holm <sunny@sunbase.org> writes:
> > - It is possible to specify a revision range, and even though all lines
> > in the file are listed, lines which changed outside this range appears
> > as empty <entry></entry> elements. That’s probably fine, but now that
> > there are line numbers in the XML, these empty elements could probably
> > be skipped to minimise the size of the output?
> I'd like to understand better what a revision range means in 'svn blame'.
> For example, you do
> $ svn blame --xml -r12:25 foo.c
> Suppose that
> - some lines Q were modified in r15 and again in r19;
Annotated by r19.

> - some lines R were added in r13, modified in r15 and r16, and
> later deleted in r20;
Not visible, since we're viewing r25.

> - some lines S were deleted in r17;
Same her.e

> - some lines T were modified in r18 and deleted in r22;

> I haven't read the patch carefully. Would revision ranges be
> prohibited unless --xml were also passed? If not, how would they be
> handled in non-xml output?
Balme with a revision range is nothing new at all.
svn blame -rQ:P path
will show you the file at revision P, with blame annotations going back to
Q. Lines not modified (or added) between Q and P (inclusive) are annotated
with dashes indicating "no info".


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 9 21:23:42 2005

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.