From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/9] Undoing conflict resolution
Date: Tue, 29 Dec 2009 13:42:29 -0800 [thread overview]
Message-ID: <1262122958-9378-1-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <7v6393mfqz.fsf@alter.siamese.dyndns.org>
This series resurrects the topic we discussed later November.
I wrote a bit about this in http://gitster.livejournal.com/43665.html but
as usual with my patches, they do come with minimum set of tests but it
contains no documentation updates. The user visible changes are:
- ls-files has a new option primarily for debugging;
- update-index has a new option --clear-resolve-undo;
- rerere has a new subcommand forget.
Junio C Hamano (9):
builtin-merge.c: use standard active_cache macros
resolve-undo: record resolved conflicts in a new index extension
section
resolve-undo: basic tests
resolve-undo: allow plumbing to clear the information
resolve-undo: "checkout -m path" uses resolve-undo information
resolve-undo: teach "update-index --unresolve" to use resolve-undo
info
rerere: remove silly 1024-byte line limit
rerere: refactor rerere logic to make it independent from I/O
rerere forget path: forget recorded resolution
Makefile | 2 +
builtin-checkout.c | 6 +
builtin-ls-files.c | 43 +++++++-
builtin-merge.c | 9 +-
builtin-read-tree.c | 2 +
builtin-rerere.c | 2 +
builtin-update-index.c | 18 +++-
cache.h | 4 +
read-cache.c | 18 +++
rerere.c | 259 +++++++++++++++++++++++++++++++++++++-------
rerere.h | 1 +
resolve-undo.c | 176 ++++++++++++++++++++++++++++++
resolve-undo.h | 16 +++
t/t2030-unresolve-info.sh | 140 ++++++++++++++++++++++++
14 files changed, 648 insertions(+), 48 deletions(-)
create mode 100644 resolve-undo.c
create mode 100644 resolve-undo.h
create mode 100755 t/t2030-unresolve-info.sh
next prev parent reply other threads:[~2009-12-29 21:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 18:58 [PATCH/RFC 0/3] git rerere unresolve file Johannes Sixt
2009-11-21 19:00 ` [PATCH/RFC 1/3] rerere: keep a list of resolved files in MERGE_RR Johannes Sixt
2009-11-21 19:01 ` [PATCH/RFC 2/3] rerere: make recording of the preimage reusable Johannes Sixt
2009-11-21 19:02 ` [PATCH/RFC 3/3] git rerere unresolve file Johannes Sixt
2009-11-22 2:53 ` [PATCH/RFC 0/3] " Junio C Hamano
2009-11-22 14:19 ` Johannes Sixt
2009-11-24 23:40 ` Nanako Shiraishi
2009-12-29 21:42 ` Junio C Hamano [this message]
2009-12-29 21:42 ` [PATCH 1/9] builtin-merge.c: use standard active_cache macros Junio C Hamano
2009-12-29 21:42 ` [PATCH 2/9] resolve-undo: record resolved conflicts in a new index extension section Junio C Hamano
2009-12-29 21:42 ` [PATCH 3/9] resolve-undo: basic tests Junio C Hamano
2009-12-29 21:42 ` [PATCH 4/9] resolve-undo: allow plumbing to clear the information Junio C Hamano
2009-12-29 21:42 ` [PATCH 5/9] resolve-undo: "checkout -m path" uses resolve-undo information Junio C Hamano
2009-12-29 21:42 ` [PATCH 6/9] resolve-undo: teach "update-index --unresolve" to use resolve-undo info Junio C Hamano
2009-12-29 21:42 ` [PATCH 7/9] rerere: remove silly 1024-byte line limit Junio C Hamano
2009-12-29 21:42 ` [PATCH 8/9] rerere: refactor rerere logic to make it independent from I/O Junio C Hamano
2009-12-29 21:42 ` [PATCH 9/9] rerere forget path: forget recorded resolution Junio C Hamano
2010-01-05 21:25 ` Johannes Sixt
2010-01-06 1:06 ` Junio C Hamano
2010-01-06 8:55 ` Johannes Sixt
2010-01-06 16:58 ` Junio C Hamano
2010-01-06 21:59 ` Junio C Hamano
2010-01-08 21:55 ` Johannes Sixt
2010-01-08 23:20 ` Junio C Hamano
2010-01-11 1:58 ` Junio C Hamano
2010-01-11 19:22 ` Johannes Sixt
2010-01-11 20:05 ` Junio C Hamano
2010-01-11 21:05 ` Johannes Sixt
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=1262122958-9378-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.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).