From: "Tim Visher" <tim.visher@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: 'Theirs' merge between branches on a binary file.
Date: Mon, 22 Dec 2008 16:16:40 -0500 [thread overview]
Message-ID: <c115fd3c0812221316y24ce0c7q29807cd349a99e83@mail.gmail.com> (raw)
In-Reply-To: <7vr63zhq4k.fsf@gitster.siamese.dyndns.org>
On Mon, Dec 22, 2008 at 4:11 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Do you mean during a conflicted merge resolution you would want to check
> their version out of the index and declare that it is the merge result?
Sure. Let me try to be a bit clearer.
I was developing on a feature branch and now want to merge back into
the master branch. Unfortunately, a binary file somewhat central to
the development effort was changed between the the feature branch and
the master branch and now there is a conflict. Obviously, I can't fix
the conflict via markers or something like that because it's a binary
file, and I know that I want the feature branch's version of the file,
not the one that it is in conflict with. How would I just select the
stage3 version of the file and add that to the index?
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
next prev parent reply other threads:[~2008-12-22 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 20:56 'Theirs' merge between branches on a binary file Tim Visher
2008-12-22 21:11 ` Junio C Hamano
2008-12-22 21:16 ` Tim Visher [this message]
2008-12-22 22:52 ` Junio C Hamano
2008-12-22 22:58 ` Tim Visher
2008-12-22 23:18 ` Junio C Hamano
2008-12-23 14:05 ` Tim Visher
2008-12-23 18:31 ` René Scharfe
2008-12-28 17:14 ` Tim Visher
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=c115fd3c0812221316y24ce0c7q29807cd349a99e83@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).