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

Re: Find out on which branch a commit was originally made

From
SRSeth Robertson <in-gitvger@baka.org>
Date
Sep 20, 2010, 05:47 UTC
Message-ID
<201009200547.o8K5ldI7010683@no.baka.org>
In-Reply-To
<4C96B97D.6030209@gmail.com>
In message <4C96B97D.6030209@gmail.com>, Artur Skawina writes:
    On 09/20/10 01:54, Seth Robertson wrote:
    > I'd like a command that would tell me the right branch something was
    > on whether it was on master or topic or whatever.  If instead of
    > "master" the branch was named "supertopic" and master commit AA had
    > child D would that make a difference?
    Like i said, "arguably". In theory, no, there is no difference. In
    practice, some branches will be more long-lived than others -- and
    certain conventions will apply. Hence, i think that answer /is/ the
    right one, in context -- that script was specifically looking for
    info on /another/ branch.
Only if the topic branch didn't have a merge on it.
         -AA-- subtopic
        /     \
       A---B---C topic
      /         \
 D---E---F---G---H---I---J---K---L---M---N master
                          \         /
                           O---P---Q another-topic

In the above example, the subtopic branch merge from AA to C prevents you from finding out what branch B is on using the original script.

    > I'm not sure how you can figure out when a branch was first created.
    > We might "know" that master is older than the others, but if this
    > commit was on another-topic and supertopic we cannot use that
    > intuition..
    > Returning all possible branch names at least gives the user somewhere
    > to start and does not give them ones which are obviously insane.
    IOW, why would the right answer for 'F' be both 'master' and
    'another-topic', but for 'B' - just 'topic'?
I agree 100% that the right answer is topic for B and master for F.

I know how to get topic for B. Finding master (and not another-topic) for F is difficult because we have to know something that I don't know how to get git to tell me: when another-topic branch was created. Using git-rev-parse another-topic....master we know what commit another-topic and master diverged, but I cannot figure out a way to discover which branch was created at that point and which branch pre-existed (obviously for master we know, but if this was a supertopic branch we would not). I thought about using merge direction for subsequent merges as a hint, but we don't know if the second branch has been permanently been merged or not, if there was a K->P merge and Q-M did not happen (yet) then we would give the wrong branch name.

If you (or anyone) can answer that question, I'll be happy to update the script. Otherwise getting both answers is as close as we can come.

					-Seth Robertson
Previous: Artur SkawinaNext: Stefan Haller
Message 17 of 33 in “Find out on which branch a commit was originally made”
  1. Stefan HallerSep 18, 2010
  2. Ævar Arnfjörð BjarmasonSep 18, 2010
  3. Ævar Arnfjörð BjarmasonSep 18, 2010
  4. Tor ArntsenSep 18, 2010
  5. Stefan HallerSep 18, 2010
  6. Artur SkawinaSep 18, 2010
  7. Stefan HallerSep 19, 2010
  8. Clemens BuchacherSep 19, 2010
  9. Artur SkawinaSep 19, 2010
  10. Stefan HallerSep 19, 2010
  11. Artur SkawinaSep 19, 2010
  12. Robin RosenbergSep 19, 2010
  13. Seth RobertsonSep 19, 2010
  14. Artur SkawinaSep 19, 2010
  15. Seth RobertsonSep 19, 2010
  16. Artur SkawinaSep 20, 2010
  17. Seth RobertsonSep 20, 2010
  18. Stefan HallerSep 20, 2010
  19. Artur SkawinaSep 20, 2010
  20. Artur SkawinaSep 20, 2010
  21. Seth RobertsonSep 21, 2010
  22. Artur SkawinaSep 21, 2010
  23. ANNOUNCE git-what-branch (was Re: Find out on which branch a commit was originally made)Seth Robertson, Sep 22, 2010
  24. Artur SkawinaSep 22, 2010
  25. Seth RobertsonSep 22, 2010
  26. Stephen BashSep 23, 2010
  27. Ævar Arnfjörð BjarmasonSep 23, 2010
  28. Artur SkawinaSep 23, 2010
  29. Artur SkawinaSep 24, 2010
  30. Seth RobertsonSep 24, 2010
  31. Seth RobertsonSep 23, 2010
  32. Stefan HallerSep 20, 2010
  33. Bryan DrewerySep 24, 2010

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.