From: "Geoff Russell" <geoffrey.russell@gmail.com>
To: sverre@rabbelier.nl
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
"Miklos Vajna" <vmiklos@frugalware.org>,
git@vger.kernel.org
Subject: Re: Guided merge with override
Date: Tue, 17 Jun 2008 08:15:50 +0930 [thread overview]
Message-ID: <93c3eada0806161545m5c6e1073q5522ce31f72be9f0@mail.gmail.com> (raw)
In-Reply-To: <bd6139dc0806161521p3667a44ble8573be1569986a0@mail.gmail.com>
Thanks everybody,
On 6/17/08, Sverre Rabbelier <alturin@gmail.com> wrote:
> On Mon, Jun 16, 2008 at 12:16 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> > The solution depends on whether *all* files in B should be taken, or only
> > those files in B where there's a merge conflict. I don't know an easy way
> > to do the former, but the latter I'd do like this:
> >
> > $ git diff --name-only | xargs git checkout B --
This looks like a manageable approach and better than the scripting I was
thinking about -- ie. scan the conflict files with perl and fix them!
Cheers,
Geoff
>
>
> Wouldn't something similar work but do a 'git ls-files' and filter it
> on files that have a merge conflict?
>
> --
> Cheers,
>
>
> Sverre Rabbelier
>
--
6 Fifth Ave,
St Morris, S.A. 5068
Australia
Ph: 041 8805 184 / 08 8332 5069
next prev parent reply other threads:[~2008-06-16 22:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 4:16 Guided merge with override Geoff Russell
2008-06-16 9:25 ` Miklos Vajna
2008-06-16 10:16 ` Johannes Sixt
2008-06-16 21:16 ` Miklos Vajna
2008-06-16 22:21 ` Sverre Rabbelier
2008-06-16 22:45 ` Geoff Russell [this message]
2008-06-17 20:04 ` Junio C Hamano
2008-06-18 15:19 ` Johannes Schindelin
2008-06-18 15:28 ` Johannes Schindelin
2008-06-18 16:31 ` Junio C Hamano
2008-06-18 19:29 ` Johannes Schindelin
2008-06-20 7:38 ` [PATCH 1/2] git-merge-file --ours, --theirs Junio C Hamano
2008-06-20 7:48 ` [PATCH 2/2] git-merge-recursive-{ours,theirs} Junio C Hamano
2008-06-20 12:58 ` Johannes Schindelin
2008-06-21 9:46 ` Junio C Hamano
2008-06-21 16:29 ` Johannes Schindelin
2008-06-21 16:56 ` Jakub Narebski
2008-06-17 6:16 ` Guided merge with override Johannes Sixt
2008-06-17 8:53 ` Sverre Rabbelier
2008-06-17 9:48 ` Johannes Schindelin
2008-06-17 9:53 ` Sverre Rabbelier
2008-06-17 10:17 ` 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=93c3eada0806161545m5c6e1073q5522ce31f72be9f0@mail.gmail.com \
--to=geoffrey.russell@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=sverre@rabbelier.nl \
--cc=vmiklos@frugalware.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).