From: Matthias Urlichs <smurf@smurf.noris.de>
To: git@vger.kernel.org
Subject: Merging and parents
Date: Tue, 05 Jul 2005 18:19:33 +0200 [thread overview]
Message-ID: <pan.2005.07.05.16.19.28.957617@smurf.noris.de> (raw)
I just had this ugly merge situation:
M
|\
| \
A B
|\/|
|/\|
C D
| /
|/
E
Suppose both the EC and the ED branch add files (not with conflicting
filenames!) which then get modified somewhere between C/D and M.
No matter which node gets picked as the parent, some files will end
up as "created on different branches" because the chosen parent doesn't
have them, even though, strictly speaking, it ain't so.
So ... what to do? Generate a list of parents, and for each file pick the
one parent where it (a) exists and (b) has the smallest diff?
Or just ignore (umm... OK, document) the problem?
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
I'm thankful I didn't believe in God, because it
would have been another thing for me to conquer.
-- Kim Goldman
next reply other threads:[~2005-07-05 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 16:19 Matthias Urlichs [this message]
2005-07-06 3:26 ` Merging and parents Linus Torvalds
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=pan.2005.07.05.16.19.28.957617@smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=git@vger.kernel.org \
/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