Giovanni Bajo <firstname.lastname@example.org> wrote:
> On 21/02/2007 21.30, Stefan Haller wrote:
> > - svn blame branchB/somefile
> > We probably want to see the original authors (with their original
> > revision numbers). However, it doesn't stop there: a typical use case
> > in our shop is to run blame on a file, and then do a diff to find out
> > why a line changed, so if blame shows me that a line was changed by
> > Alice in r12, I would typically run "svn diff -r11:12 somefile" to see
> > the diff. This wouldn't work here, which I consider a serious
> > problem. To solve this, the blame output would have to contain not
> > only the author and revision number of the original commit, but also
> > the path where the original commit happened.
> I think that this kind of automation can be demanded to an external GUI tool.
> Inspecting the blame history of a file with a GUI tool (like TortoiseSVN
> partly does and could be even better) is vastly superior to using a console
> for the quickness of interaction, and can handle this kind of heuristic
> automatically for the user.
Yes, we do use an external GUI tool for this (ViewVC, most of the time,
which has convenient links to the respective diff), but it doesn't
really matter: whether it's me doing it manually on the command line, or
a GUI tool providing shortcuts for it, in either case the blame API must
provide the necessary information (the path of the original commit, in
this case). I don't see how this particular case could be solved by
applying heuristics (but maybe I'm missing something).
> Moreover, if we had a way (before SVN 5.0...) to specify the repository root
> with a quick shortcut like svk does ("//" or whatever syntax can make people
> agree), it would be sufficient to "svn diff -c12 //" in your case to get what
> you want.
No, that's not the same. I don't want to see the entire diff of the
whole revision, I only want to see the diff for the single file I was
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Feb 22 14:36:14 2007