On Sun, 17 Dec 2006, Junio C Hamano wrote: > > - blame A..B's output shows lines attributed to the boundary > commit with commit SHA-1 prefixed with '^'; I wonder if it would make sense to have a flag or mode or something where boundary commit attributions are simply left unattributed (ie just leave that _empty_). Same goes for some way of telling git blame that the root commit is uninteresting (it's a "boundary commit by definition" in the import case). For the kernel, when I do a "git blame" on a file, if it gets blamed on the root commit, it really isn't a valid blame line at all - I'd prefer to have it show up as "no blame" rather than have it show up as being blamed on a specific commit of mine. (But that would be true only for a _real_ root, not the pseudo-"root" that comes from stopping commit tracing due to the file not existing in any of the parents). Hmm? Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html