Re: [RFD] Explicitly documenting patch submission

[Dave Jones]

On Fri, May 28, 2004 at 11:07:40AM -0400, Theodore Ts'o wrote:
 > On Fri, May 28, 2004 at 06:24:36AM -0700, Larry McVoy wrote:
 > > Not in any useful way.  If I go look at the file history, which is what
 > > I'm going to do when tracking down a bug, all I see on the files included
 > > in this changeset is akpm@xxxxxxxxx
 > > 
 > > That means any annotated listing (BK or CVS blame) shows the wrong author.
 > 
 > One of the ways that I often use for tracking down potential fixes is
 > to simply do "bk changes > /tmp/foo" and then use emacs's incremental
 > search to look for interesting potential changes.  (I know, you're
 > probably throwing up all over your keyboard just about now.  :-)
 > 
 > One "interesting" thing I've wished for is to be able to do "bk
 > revtool drivers/net/wireless/airo.c", and then when I put my mouse
 > over a particular line number, have it display in a little popup box 
 > the changelog description of whatever line my mouse happened to 
 > be over.

bk revtool $filename
ctrl-c in the gui that pops up
click line that looks interesting - jumps to the cset with
commit comments.

That what you meant ?

		Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/