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

RE: svn blame -r REV

From: John Szakmeister <jszakmeister_at_actelesys.com>
Date: 2003-11-03 20:19:15 CET

That's exactly what I'm proposing. I'll see if I can hack that in tonight.

Thanks!

-John

-----Original Message-----
From: kfogel@collab.net [mailto:kfogel@collab.net]
Sent: Monday, November 03, 2003 12:32 PM
To: John Szakmeister
Cc: Subversion Development List
Subject: Re: svn blame -r REV

John Szakmeister <john@szakmeister.net> writes:
> I actually pointed it out in this message:
> http://www.contactor.se/~dast/svn/archive-2003-10/1608.shtml

Sorry -- I knew there had been a thread about this, and remembered
with regret that I hadn't followed it closely enough at the time :-).

> But no one piped in to say why they made it work that way. It appears
that
> when you specify a revision, it actually starts generating the annotation
> *from* that revision to HEAD. I think it should start from 1 and go to
the
> rev you specify (which is what I think you wanted too). I can make a
patch
> and fix that, but I was hoping to get a little guidance from someone that
it
> was the Right Thing To Do.

I completely agree, as does Mike Pilato (who sat with me as we
stumbled through our intuition into the real behavior).

So what you're proposing is:

   svn blame foo.c behaves as currently
   svn blame -rN foo.c behaves like 'svn blame -r1:N foo.c'
   svn blame -rN:M foo.c behaves as currently

right?

If so, +1 all over that.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 3 20:28:02 2003

This is an archived mail posted to the Subversion Dev mailing list.