From: David Kastrup Date: Fri, 09 May 2014 05:04:05 GMT Subject: Re: Output from "git blame A..B -- path" for the bottom commit is misleading Message-ID: <87zjiro856.fsf@fencepost.gnu.org> In-Reply-To: <20140509001145.GA8734@sigill.intra.peff.net> Jeff King writes: > I'd actually be inclined to say the opposite of what Junio is saying > there: that "-b" should blank the author field as well as the commit > sha1. I'd even go so far as to say that "-b" should probably be the > default when boundary commits are in use. I cannot think of a time when > I have found the boundary information useful, and the IMHO the output > above is less confusing than what we produce now. But I admit I haven't > thought very hard on it. Arguably if the user explicitly limited the range, he knows what he's looking at. Admittedly, I don't know offhand which options _will_ produce boundary commit indications: there may be some without explicit range limitation, and we might also be talking about limiting through shallow repos (git blame on a shallow repo is probably a bad idea in the first place, but anyway). -- David Kastrup