Sean wrote: > Only merging the branches will make the commit show up in branch B with > the same SHA1 number (or identity) that it had in branch A. This is a > fundamental part of Git. The sha1 of each commit is based in part on > the sha1 of its parent. Thus it's impossible[1] to copy a commit to > another branch (ie. reparent it) without changing its identity. > > Sean > > [1] Okay, more or less impossible.. don't ask me do the math. Ah, I didn't see the wood for the trees. And this dependence of a commit's identity on the history is also a (or the) reason why mergers are necessarily spliced in as commits with unique identity too... -- Stefan Richter -=====-=-==- =-=- --==- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html