From: Joshua Jensen <jjensen@workspacewhiz.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Sharing a massive distributed merge
Date: Wed, 16 Mar 2011 14:12:46 -0600 [thread overview]
Message-ID: <4D8119BE.2090208@workspacewhiz.com> (raw)
We have two codelines that diverged quite a while back, and we are now
bringing them back together. More than 800 files are in conflict, but
it is very possible that the automatic non-conflicting merge is not
correcting. This means thousands of files need to be examined.
Git doesn't support distribution of a merge (although that would be
extraordinarily cool), so the next best thing seemed to be force adding
all files with conflict markers and then committing the merge. We then
publish the conflicting branch and have each person fix their files.
Given that the conflict markers are already in place, they can't use
their favorite graphical merge tool.
What I want to be able to do is have each person perform the merge
locally, stage only the files they care about in that session, reset all
other files, and commit as a regular commit, not a merge commit. The
user can take advantage of whatever tools they want in the in progress
merge. When everyone has finished this process, we run git merge and
keep our local changes.
I have had no success in doing the above. Is there a fancy way to pull
this off with Git?
Thanks.
Josh
next reply other threads:[~2011-03-16 20:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 20:12 Joshua Jensen [this message]
2011-03-17 5:21 ` Sharing a massive distributed merge Jay Soffian
2011-03-17 6:38 ` Jeff King
2011-03-17 7:04 ` Jay Soffian
2011-03-17 7:30 ` Jeff King
2011-03-18 5:49 ` Jeff King
2011-03-24 3:03 ` Joshua Jensen
2011-03-17 8:53 ` Alex Riesen
2011-03-17 14:10 ` Jay Soffian
2011-03-17 14:54 ` Alex Riesen
2011-03-17 17:58 ` Jay Soffian
2011-03-17 18:48 ` Alex Riesen
2011-03-17 19:15 ` Jeff King
2011-03-17 19:53 ` Alex Riesen
2011-03-17 20:54 ` Junio C Hamano
[not found] ` <10061287.5697.1300343903667.JavaMail.trustmail@mail1.terreactive.ch>
2011-03-17 7:51 ` Where do all the tips go? (Was: Re: Sharing a massive distributed merge) Victor Engmark
2011-03-17 8:01 ` Jeff King
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=4D8119BE.2090208@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--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;
as well as URLs for NNTP newsgroup(s).