Re: How to find the first commit belonging to any branch

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: How to find the first commit belonging to any branch

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:59

Kristian Amlie [off-list ref] writes:
I have a question about git: I have one commit sha1, and I would like
to know the nearest commit that appears in *any* other branch. The
sha1 that I have does not belong to any branch.

The obvious thing to do would be to make a for loop and iterate over
existing branches while calling git merge-base, but I'm wondering if
there's a more clever method.
If the $commit does not belong to any branch, then:

    $ git rev-list --bounardy $commit^0 --not --branches | sed -ne 's/^-//p'

would give you boundary commits of the above traversal, which says:

    Traverse from $commit following the parents, but stop at anything that
    is reachable from any breanch.

which means that the ones that are output are the candidates that are on
some branch.

So pipe that to name-rev like this, perhaps (untested)?

    $ git rev-list --bounardy $commit^0 --not --branches |
      sed -ne 's/^-//p' |
      git name-rev --stdin

Re: How to find the first commit belonging to any branch

From: Kristian Amlie <hidden>
Date: 2016-06-15 22:44:59

Junio C Hamano wrote:
Kristian Amlie [off-list ref] writes:
quoted
I have a question about git: I have one commit sha1, and I would like
to know the nearest commit that appears in *any* other branch. The
sha1 that I have does not belong to any branch.

The obvious thing to do would be to make a for loop and iterate over
existing branches while calling git merge-base, but I'm wondering if
there's a more clever method.
If the $commit does not belong to any branch, then:

    $ git rev-list --bounardy $commit^0 --not --branches | sed -ne 's/^-//p'

would give you boundary commits of the above traversal, which says:

    Traverse from $commit following the parents, but stop at anything that
    is reachable from any breanch.

which means that the ones that are output are the candidates that are on
some branch.

So pipe that to name-rev like this, perhaps (untested)?

    $ git rev-list --bounardy $commit^0 --not --branches |
      sed -ne 's/^-//p' |
      git name-rev --stdin
Thanks! That did the trick!

Kristian
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help