From: Duy Nguyen <pclouds@gmail.com>
To: Stefan Beller <sbeller@google.com>,
Michael Haggerty <mhagger@alum.mit.edu>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Find a topic branch containing a commit
Date: Wed, 27 Jul 2016 20:03:15 +0200 [thread overview]
Message-ID: <CACsJy8CKLmjW82TJHUoqrM1smmiP=dcDqvOpN_QDPePEy0ZuJw@mail.gmail.com> (raw)
In-Reply-To: <CAGZ79kY5UrjSj8xbjB+MvTE2xUyt+te1RKN6Bf0WiEA23iZ7wg@mail.gmail.com>
On Wed, Jul 27, 2016 at 7:50 PM, Stefan Beller <sbeller@google.com> wrote:
> On Wed, Jul 27, 2016 at 10:42 AM, Duy Nguyen <pclouds@gmail.com> 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. 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.
--
Duy
next prev parent reply other threads:[~2016-07-27 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 17:42 Find a topic branch containing a commit Duy Nguyen
2016-07-27 17:50 ` Stefan Beller
2016-07-27 18:02 ` Stefan Beller
2016-07-27 18:07 ` Duy Nguyen
2016-07-27 18:03 ` Duy Nguyen [this message]
2016-07-28 13:46 ` Michael Haggerty
2016-07-28 15:11 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8CKLmjW82TJHUoqrM1smmiP=dcDqvOpN_QDPePEy0ZuJw@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).