From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 00/12] Towards a better merge resolution support
Date: Mon, 1 Sep 2008 13:34:16 +0200 [thread overview]
Message-ID: <20080901113416.GA8610@blimp.localhost> (raw)
In-Reply-To: <7vod38w3q6.fsf@gitster.siamese.dyndns.org>
Junio C Hamano, Mon, Sep 01, 2008 12:38:25 +0200:
> Alex Riesen <raa.lkml@gmail.com> writes:
>
> > ... IOW, copy the commit
> > resolution from some other merge commit. Maybe can be a way to use
> > rerere mechanism with that?
>
> If you know which merge I did you want to steal from, you can prime your
> rerere database by pretending to be me, doing the merge. Something like:
>
> $ git checkout $merge^1 ;# detach to the parent of merge
> $ git merge $merge^2 ;# pretend you were me to redo it
> $ git diff -R $merge | git apply --index ;# and get what I did
I ended up using
$ git checkout Merge^1
$ git merge Merge^2
$ git diff -R Merge | git apply
$ git diff -R Merge --name-only -z | git update-index -z --stdin
$ git rerere
Just git apply --index complained about the files missing from the
index:
$ git tag Merge c5e2ace70271b481632aaf987361027ca4592df6
$ gco Merge^1
Previous HEAD position was c5e2ace... Merge branch 'jc/better-conflict-resolution' into next
HEAD is now at 2392877... Merge branch 'master' into next
$ git merge Merge^2
Auto-merging Documentation/config.txt
Auto-merging Documentation/git-checkout.txt
CONFLICT (content): Merge conflict in Documentation/git-checkout.txt
Auto-merging builtin-checkout.c
CONFLICT (content): Merge conflict in builtin-checkout.c
Auto-merging builtin-merge-recursive.c
Auto-merging t/t6023-merge-file.sh
Auto-merging t/t7201-co.sh
CONFLICT (content): Merge conflict in t/t7201-co.sh
Auto-merging xdiff-interface.c
Auto-merging xdiff-interface.h
Recorded preimage for 'Documentation/git-checkout.txt'
Recorded preimage for 'builtin-checkout.c'
Recorded preimage for 't/t7201-co.sh'
Automatic merge failed; fix conflicts and then commit the result.
$ git diff -R Merge |git apply --index
error: Documentation/git-checkout.txt: does not exist in index
error: builtin-checkout.c: does not exist in index
error: t/t7201-co.sh: does not exist in index
> $ git rerere ;# have rerere record the resolution
Well, it works, but it's a bit of work and hard to automate (needs a
working tree). An option to merge:
$ git merge <branch>
conflict ... investigate ... find a resolution in <resolution>
$ git reset --hard
$ git merge --rerere <resolution> branch
check... Ok.
$ git commit
or rerere:
$ git merge <branch>
conflict ... investigate ... find a resolution in <resolution>
$ git rerere <resolution>
$ git reset --hard
$ git merge <branch>
check... Ok.
$ git commit
These could be more convenient.
next prev parent reply other threads:[~2008-09-01 11:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 0:42 [PATCH 00/12] Towards a better merge resolution support Junio C Hamano
2008-08-30 0:42 ` [PATCH 01/12] xdl_fill_merge_buffer(): separate out a too deeply nested function Junio C Hamano
2008-08-30 0:42 ` [PATCH 02/12] xdiff-merge: optionally show conflicts in "diff3 -m" style Junio C Hamano
2008-08-30 0:42 ` [PATCH 03/12] xmerge.c: minimum readability fixups Junio C Hamano
2008-08-30 0:42 ` [PATCH 04/12] xmerge.c: "diff3 -m" style clips merge reduction level to EAGER or less Junio C Hamano
2008-08-30 0:42 ` [PATCH 05/12] rerere.c: use symbolic constants to keep track of parsing states Junio C Hamano
2008-08-30 0:42 ` [PATCH 06/12] rerere: understand "diff3 -m" style conflicts with the original Junio C Hamano
2008-08-30 0:42 ` [PATCH 07/12] merge.conflictstyle: choose between "merge" and "diff3 -m" styles Junio C Hamano
2008-08-30 0:42 ` [PATCH 08/12] git-merge-recursive: learn to honor merge.conflictstyle Junio C Hamano
2008-08-30 0:42 ` [PATCH 09/12] checkout: do not check out unmerged higher stages randomly Junio C Hamano
2008-08-30 0:42 ` [PATCH 10/12] checkout: allow ignoring unmerged paths when checking out of the index Junio C Hamano
2008-08-30 0:42 ` [PATCH 11/12] checkout --ours/--theirs Junio C Hamano
2008-08-30 0:42 ` [PATCH 12/12] checkout -m: recreate merge when checking out of unmerged index Junio C Hamano
2008-08-30 9:42 ` [PATCH 07/12] merge.conflictstyle: choose between "merge" and "diff3 -m" styles Johannes Schindelin
2008-08-30 9:34 ` [PATCH 04/12] xmerge.c: "diff3 -m" style clips merge reduction level to EAGER or less Johannes Schindelin
2008-08-30 9:31 ` [PATCH 03/12] xmerge.c: minimum readability fixups Johannes Schindelin
2008-08-30 15:42 ` Junio C Hamano
2008-08-30 9:29 ` [PATCH 02/12] xdiff-merge: optionally show conflicts in "diff3 -m" style Johannes Schindelin
2008-08-30 9:14 ` [PATCH 01/12] xdl_fill_merge_buffer(): separate out a too deeply nested function Johannes Schindelin
2008-09-01 9:39 ` [PATCH 00/12] Towards a better merge resolution support Alex Riesen
2008-09-01 9:44 ` Alex Riesen
2008-09-01 9:50 ` Abhijit Menon-Sen
2008-09-01 12:20 ` Thomas Rast
2008-09-01 10:38 ` Junio C Hamano
2008-09-01 11:34 ` Alex Riesen [this message]
2008-09-01 17:26 ` Junio C Hamano
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=20080901113416.GA8610@blimp.localhost \
--to=raa.lkml@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).