On Thu, Aug 07, 2008 at 08:09:40AM +0200, Alex Riesen wrote: > Steven Grimm, Thu, Aug 07, 2008 00:18:33 +0200: > > What, if any, is the approved way to get git blame to follow cherry- > > picked changes? > > The can't be any: cherry-picks are just new commits. You just make the > same changes at the new place in the history. We used to say "cherry-picked from..." in the commit message, but I don't think we do by default any longer. One could follow that link to see the original change (if it still exists!). You could potentially have git-blame incorporate that information (again, if the referenced commit is even still available), but I'm not sure exactly what difference it would make. I don't think you would want to start blaming up the original commits line of parentage. -Peff -- 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
