Vincent Ladeuil wrote:This refers to the parents of a _commit_, not of a tree, and the parents must be _commits_. The parents allow us to determine what changed between the previous commit(s), and the current one. If there are more than one parent, then we have a merge commit. So, a commit refers to a tree representing the state of the code at the time of the commit, as well as to any parent commit(s). If there are no parent commits, then the commit is an "initial commit" (i.e. the first checkin). A project can have multiple "initial commits", typically where two previously independent projects are merged together, c.f. gitk and git. Yes. Yes. That is exactly right. From there, we can either trivially merge CA and CB with a new merge commit referring to T2, but citing both CA and CB as parents, or simply discard one of the lines of development, depending on how much subsequent development cited CA or CB as parents. Rogan - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| FUJITA Tomonori | Re: Linux 2.6.25-rc4 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Artem Bityutskiy | [PATCH 11/44 take 2] [UBI] allocation unit header |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
