From: Jonathan Nieder <jrnieder@gmail.com>
To: Stephen Boyd <bebarino@gmail.com>
Cc: git@vger.kernel.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: [PATCH 11/16] revert_or_cherry_pick(): get oneline_body from get_oneline()
Date: Wed, 17 Mar 2010 22:16:38 -0500 [thread overview]
Message-ID: <20100318031638.GA18193@progeny.tock> (raw)
In-Reply-To: <780e0a6b1003171309k75b33d3cpb4b1c6370d67942f@mail.gmail.com>
Stephen Boyd wrote:
> Could all this code just use the custom format printing routines in
> pretty.c? It might not be super efficient but at least it wouldn't
> duplicate a bunch of code.
I like this idea, but I wasn’t able to pull it off. You see,
cmd_revert() uses a few substrings from a single string it generates:
parent of ca87ef9... Do something very imporant
^ ^ ^
1 2 3
These are put together like so:
For the commit message:
Subject: Revert "[3]Do something very important"
This reverts commit ca87ef90000000000000000000000000000000000.
For the conflict markers:
<<<<<<< HEAD
Version from the tip of the current branch.
||||||| [2]ca87ef9... Do something very important
Version from the commit to be reverted.
=======
Version from the parent of the commit to be reverted.
>>>>>>> [1]parent of ca87ef9... Do something very important
Nevertheless, investigating it did spur me to simplify this part of the
series a little. I think the following two patches could replace
patches 11, 13, 14, and 15 from this thread. I do not want to do any
drastic refactoring without libifying this code, though, and that should
wait for another series, I think.
Thanks for the feedback.
Jonathan Nieder (2):
revert: clarify label on conflict hunks
cherry-pick, revert: add a label for ancestor
builtin/revert.c | 129 +++++++++++++++++++++++----------------
t/t3507-cherry-pick-conflict.sh | 8 +-
2 files changed, 80 insertions(+), 57 deletions(-)
next prev parent reply other threads:[~2010-03-18 3:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 11:36 [PATCH v2 0/16] Add label for common ancestor to conflictstyle=diff3 Jonathan Nieder
2010-03-17 11:46 ` [PATCH 01/16] xdl_merge(): add optional ancestor label to diff3-style output Jonathan Nieder
2010-03-17 14:22 ` Bert Wesarg
2010-03-20 22:47 ` Jonathan Nieder
2010-03-17 11:53 ` [PATCH 02/16] xdl_merge(): move file1 and file2 labels to xmparam structure Jonathan Nieder
2010-03-17 11:57 ` [PATCH 03/16] merge-file --diff3: add a label for ancestor Jonathan Nieder
2010-03-17 12:03 ` [PATCH 04/16] ll_merge(): add ancestor label parameter for diff3-style output Jonathan Nieder
2010-03-17 12:04 ` [PATCH 05/16] checkout --conflict=diff3: add a label for ancestor Jonathan Nieder
2010-03-17 12:05 ` [PATCH 06/16] merge_file(): add comment explaining behavior wrt conflict style Jonathan Nieder
2010-03-17 12:08 ` [PATCH 07/16] merge_trees(): add ancestor label parameter for diff3-style output Jonathan Nieder
2010-03-17 12:09 ` [PATCH 08/16] tests: document format of conflicts from checkout -m Jonathan Nieder
2010-03-17 12:13 ` [PATCH 09/16] checkout -m --conflict=diff3: add a label for ancestor Jonathan Nieder
2010-03-17 12:13 ` [PATCH 10/16] tests: document cherry-pick behavior in face of conflicts Jonathan Nieder
2010-03-17 12:15 ` [PATCH 11/16] revert_or_cherry_pick(): get oneline_body from get_oneline() Jonathan Nieder
2010-03-17 20:09 ` Stephen Boyd
2010-03-18 3:16 ` Jonathan Nieder [this message]
2010-03-18 3:33 ` [PATCH 11,13,14 v2] revert: clarify label on conflict hunks Jonathan Nieder
2010-03-18 3:34 ` [PATCH 15/16 v2] cherry-pick, revert: add a label for ancestor Jonathan Nieder
2010-03-17 12:16 ` [PATCH 12/16] compat: add mempcpy() Jonathan Nieder
2010-03-17 12:17 ` [PATCH 13/16] revert: simplify get_oneline() using mempcpy Jonathan Nieder
2010-03-17 12:19 ` [PATCH 14/16] revert: clarify label on conflict hunks Jonathan Nieder
2010-03-17 12:23 ` [PATCH 15/16] cherry-pick: add a label for ancestor Jonathan Nieder
2010-03-17 12:26 ` [PATCH 16/16] merge-recursive: " Jonathan Nieder
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=20100318031638.GA18193@progeny.tock \
--to=jrnieder@gmail.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=monnier@iro.umontreal.ca \
/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).