On 07/27/2016 08:03 PM, Duy Nguyen wrote: > On Wed, Jul 27, 2016 at 7:50 PM, Stefan Beller <sbeller@xxxxxxxxxx> wrote: >> On Wed, Jul 27, 2016 at 10:42 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote: >>> Before I start doing anything silly because I don't know it can >>> already be done without waving my C wand like a mad man... >>> >>> I often do this: find a commit of interest, the commit itself is not >>> enough so I need a full patch series to figure out what's going, so I >>> fire up "git log --graph --oneline" and manually search that commit >>> and trace back to the merge point, then I can "git log --patch". Is >>> there an automatic way to accomplish that? Something like "git branch >>> --contains" (or "git merge --contains")? >> >> https://github.com/mhagger/git-when-merged ? > > Beautiful. If it had an option to show a topic (i.e. git-log from > merge base to merge point) I would be ecstatic. That's a good idea. I just created a pull request to add that feature: https://github.com/mhagger/git-when-merged/pull/13 Let me know what you think! > Michael, any plans on > bringing this in C Git? For many topic-based projects this would be > very helpful addition, and I think it's not so hard to do it in C > either. I had no such plans, and I don't have time to work on that now. But I certainly don't object if somebody else wants to work on it. It might make a nice GSoC-sized project (though I'm not volunteering to be a mentor at this time :-P ). Michael -- 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