From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: Commit to more than one branch at once?
Date: Fri, 06 Oct 2006 21:23:59 +0200 [thread overview]
Message-ID: <4526AD4F.70305@s5r6.in-berlin.de> (raw)
In-Reply-To: <BAYC1-PASMTP020F3D66B3E46CDBE82D40AE130@CEZ.ICE>
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/
next prev parent reply other threads:[~2006-10-06 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 18:18 Commit to more than one branch at once? Stefan Richter
2006-10-06 18:37 ` Linus Torvalds
[not found] ` <20061006143804.abb6c321.seanlkml@sympatico.ca>
2006-10-06 18:38 ` Sean
2006-10-06 19:23 ` Stefan Richter [this message]
2006-10-06 18:52 ` Petr Baudis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4526AD4F.70305@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox