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

Re: newb: Given a commit id, find which branches have it as an ancestor

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 13, 2009, 07:37 UTC
Message-ID
<7v3adhj2ku.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<49BA07E5.2080701@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
Show 5 quoted lines
> Your best bet is perhaps that you create a branch at the commit
>
>   $ git branch tmp-branch your_sha1
>
> so that the commits are not lost, then you cherry-pick them to master.

It could be that there are more commits that are built on top of the one you are aware of. Finding unreachable commits from "git fsck --full" might help you find them.

Previous: Johannes SixtNext: Kelly F. Hickel
Message 3 of 5 in “RE: newb: Given a commit id, find which branches have it as an ancestor”
  1. Kelly F. HickelMar 12, 2009
  2. Johannes SixtMar 13, 2009
  3. Junio C HamanoMar 13, 2009
  4. Kelly F. HickelMar 13, 2009
  5. Kelly F. HickelMar 13, 2009

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.