From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Struggling with tangled
Date: Wed, 22 Nov 2006 03:57:07 -0800 [thread overview]
Message-ID: <7vu00rsnho.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0611221233370.30004@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Wed, 22 Nov 2006 12:35:52 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> On Wed, 22 Nov 2006, Alan Chandler wrote:
>
>> 2) Some files get completely munged with conflict resolution markers
>> every few lines. Is there a simple way to say "don't use this file, but
>> use the [stage2/stage3] sources of the merge". (ie one of the original
>> inputs to the merge - and if so, which one is which)
>
> I find myself using
>
> git diff --ours <file>
>
> and
>
> git diff --theirs <file>
>
> in such a case sometimes. If I _know_ my version is good, I do
>
> git diff --ours <file> | git apply -R
>
> This also updates the index.
Good suggestion, but apply does not update the index without
being told to do so with --index, so I think the commandline
should be:
git diff --ours <path> | git apply -R --index
next prev parent reply other threads:[~2006-11-22 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 10:37 Struggling with tangled Alan Chandler
2006-11-22 11:01 ` Jakub Narebski
2006-11-22 19:15 ` Alan Chandler
2006-11-22 19:40 ` Jakub Narebski
2006-11-22 11:35 ` Johannes Schindelin
2006-11-22 11:57 ` Junio C Hamano [this message]
2006-11-22 13:30 ` Johannes Schindelin
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=7vu00rsnho.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.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