git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Find a topic branch containing a commit

From
Duy Nguyen <pclouds@gmail.com>
Date
Jul 27, 2016, 17:42 UTC
Message-ID
<CACsJy8CMnywB8AdmLxB8LnsznHrMTieoezhaQS=2r1pnM8ONZA@mail.gmail.com>

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")?

PS. Sometimes I wish we could optionally save cover letter in the merge commit. Sometimes the "big plan" is hard to see by reading individual commit messages.

-- 
Duy
Next: Stefan Beller
Message 1 of 7 in “Find a topic branch containing a commit”
  1. Duy NguyenJul 27, 2016
  2. Stefan BellerJul 27, 2016
  3. Stefan BellerJul 27, 2016
  4. Duy NguyenJul 27, 2016
  5. Duy NguyenJul 27, 2016
  6. Michael HaggertyJul 28, 2016
  7. Junio C HamanoJul 28, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.