GIT – How to know the branch a branch branched from?

Support I create multiple branches (aaa, bbb, ccc) from a commit. Then, I create a new branch (ddd) from one of the branch (bbb) and a make a commit on it.

Then I pushed everything to a remote. How would another person knows the new branch (ddd) comes from which branch?

The git commands I did was:

git branch aaa

git branch bbb

git branch ccc

git branch ddd bbb

git checkout ddd

echo 2 >> file

git add file

git commit -m “2”

And the git log would show

* commit d259a3b (HEAD, ddd)

|

| 2

|

* commit efb038c (develop, ccc, bbb, aaa)

|

| 1

|

* commit dd24bb6 (master)

It is even possible to know that ddd was branched from bbb?

Thanks

  • Working in Git Branch, and then deciding a need a new branch, some files already committed
  • Git, tell me when a remote branch that I am tracking is removed
  • Git not pushing correctly for Github gh-pages
  • GIT - Where did I branch from?
  • How to pull remote Git master if it doesn't exist locally?
  • Using Git, show all commits that are in one branch, but not the other(s)
  • Checkout recently created branch
  • Git dealing with large amounts of files which shouldn't be checked into svn
  • 3 Solutions collect form web for “GIT – How to know the branch a branch branched from?”

    It is indeed impossible in general. Git records only1 the single commit-ID (SHA-1) to which a reference name (such as a branch or tag) points. The history of that commit is determined solely by that commit’s parent IDs, which do not record branch-names. When you push to a remote, your “push” operation sends the SHA-1 of the commit you’re pushing (plus more SHA-1s for any other linked objects—trees and files, parent commits, etc—plus the contents of all those objects, as needed based on what’s missing on the remote), and asks the remote to set its branch to point to the new SHA-1.

    In other words, you tell the remote: “here, have commit 1234567, and set branch label ddd = 1234567″. It may tell you “to do that I need five other commits”, one of which you have labeled as bbb, but if you don’t tell the remote “oh by the way set label bbb to this other commit too” then it won’t have that information anywhere.


    1This is a bit of an overstatement: git also records, in the reflog, each SHA-1 that is stored in a label, including branch labels. It is therefore possible to walk back through the label’s history to “figure out where it started”. There are two limits on this though: reflogs are purely local, never transmitted by fetch or push; and reflogs expire, generally after 90 days in these cases (although this is configurable and there are additional complexities). So as long as we say there’s a push step, or allow more than 3 months to pass, there’s no way to tell.

    Branches are nothing more than pointers to a specific commit. You can only see from which commit ddd was branched from, not which branch.

    Branches are simply pointers to commits. Because of this, it is not possible to see where a branch originated from, other than observing that two branches have an identical history up to some point.

    For someone upstream, it is not relevant where a branch originated from, only that it contains a certain commit (or sequence of commits). This determines how/if git is able to fast-forward or merge branches together.

    Git Baby is a git and github fan, let's start git clone.