From: Denton Liu <liu.denton@gmail.com>
To: phillip.wood@dunelm.org.uk
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: [PATCH v8 08/11] merge: cleanup messages like commit
Date: Tue, 19 Mar 2019 23:32:15 -0700 [thread overview]
Message-ID: <20190320063215.GA9432@archbookpro.localdomain> (raw)
In-Reply-To: <304e99ef-553c-f538-f1d8-aaa0937da62f@gmail.com>
Hi Phillip,
On Tue, Mar 19, 2019 at 11:13:37AM +0000, Phillip Wood wrote:
> Hi Denton
>
> On 17/03/2019 10:16, Denton Liu wrote:
> > This change allows git-merge messages to be cleaned up with the
> > commit.cleanup configuration or --cleanup option, just like how
> > git-commit does it.
> >
> > We also give git-pull the passthrough option of --cleanup so that it can
> > also take advantage of this change.
> >
> > Finally, add testing to ensure that messages are properly cleaned up.
> > Note that some newlines that were added to the commit message were
> > removed so that if a file were read via -F, it would be copied
> > faithfully.
> >
> > Reviewed-by: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> I'd echo Eric's comments about Reviewed-by tags.
Will do.
>
> > Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>
> > Signed-off-by: Denton Liu <liu.denton@gmail.com>
> > ---
> >
> > Phillip Wood wrote:
> > > cleanup needs to take an argument so PARSE_OPT_NOARG does not look
> > > right. Also I think it would be bettor from the user's point of view if
> > > the value of the argument was checked by pull before it does any work
> > > rather otherwise if they pass in invalid value pull mostly runs and then
> > > merge errors out at the end.
> >
> > I opted not to do a check on the validity of the value of the
> > --cleanup-mode argument because the strategy options that existed before
> > also didn't verify the validity of their values. In the future, it might
> > be a good idea to check the values of both cleanup-mode and the
> > strategy options but for now, I think we can leave it as it is.
>
> With --strategy-option the valid values depend on the --strategy option
> which may invoke an external command so in general there is no way to check
> the values are valid (it could do for the strategies we know about). With
> --cleanup we know the valid values and have a function that can check for
> them so I think it would be worth doing.
Makes sense, I'll do it (and throw in a test case for free ;) )
>
> > Documentation/merge-options.txt | 5 +++
> > builtin/merge.c | 31 +++++++++++----
> > builtin/pull.c | 6 +++
> > t/t7604-merge-custom-message.sh | 67 +++++++++++++++++++++++++++++++++
> > wt-status.c | 12 ++++--
> > wt-status.h | 1 +
> > 6 files changed, 112 insertions(+), 10 deletions(-)
> >
> > diff --git a/Documentation/merge-options.txt b/Documentation/merge-options.txt
> > index 92a7d936c1..646100ea9a 100644
> > --- a/Documentation/merge-options.txt
> > +++ b/Documentation/merge-options.txt
> > @@ -32,6 +32,11 @@ they run `git merge`. To make it easier to adjust such scripts to the
> > updated behaviour, the environment variable `GIT_MERGE_AUTOEDIT` can be
> > set to `no` at the beginning of them.
> > +--cleanup=<mode>::
> > + This option determines how the merge message will be cleaned up
> > + before commiting or being passed on. See linkgit:git-commit[1] for more
>
> As I commented before I don't understand 'passed on'
I changed it in git-revert.txt and git-cherry-pick.txt but I forgot to
change it here. What do you think about this:
--cleanup=<mode>::
This option determines how the merge message will be cleaned up
before commiting or being passed on to the commit machinery. See
linkgit:git-commit[1] for more details.
>
> > + details.
> > +
> > --ff::
> > When the merge resolves as a fast-forward, only update the branch
> > pointer, without creating a merge commit. This is the default
> > diff --git a/builtin/merge.c b/builtin/merge.c
> > index 5ce8946d39..7be03a2610 100644
> > --- a/builtin/merge.c
> > +++ b/builtin/merge.c
> > @@ -38,6 +38,7 @@
> > #include "tag.h"
> > #include "alias.h"
> > #include "commit-reach.h"
> > +#include "wt-status.h"
> > #define DEFAULT_TWOHEAD (1<<0)
> > #define DEFAULT_OCTOPUS (1<<1)
> > @@ -98,6 +99,9 @@ enum ff_type {
> > static enum ff_type fast_forward = FF_ALLOW;
> > +static const char *cleanup_arg;
> > +static enum commit_msg_cleanup_mode cleanup_mode;
> > +
> > static int option_parse_message(const struct option *opt,
> > const char *arg, int unset)
> > {
> > @@ -249,6 +253,7 @@ static struct option builtin_merge_options[] = {
> > N_("perform a commit if the merge succeeds (default)")),
> > OPT_BOOL('e', "edit", &option_edit,
> > N_("edit message before committing")),
> > + OPT_CLEANUP(&cleanup_arg),
> > OPT_SET_INT(0, "ff", &fast_forward, N_("allow fast-forward (default)"), FF_ALLOW),
> > OPT_SET_INT_F(0, "ff-only", &fast_forward,
> > N_("abort if fast-forward is not possible"),
> > @@ -612,6 +617,8 @@ static int git_merge_config(const char *k, const char *v, void *cb)
> > return git_config_string(&pull_twohead, k, v);
> > else if (!strcmp(k, "pull.octopus"))
> > return git_config_string(&pull_octopus, k, v);
> > + else if (!strcmp(k, "commit.cleanup"))
> > + return git_config_string(&cleanup_arg, k, v);
> > else if (!strcmp(k, "merge.renormalize"))
> > option_renormalize = git_config_bool(k, v);
> > else if (!strcmp(k, "merge.ff")) {
> > @@ -797,23 +804,32 @@ static void abort_commit(struct commit_list *remoteheads, const char *err_msg)
> > exit(1);
> > }
> > +static const char comment_line_explanation[] =
> > +N_("Lines starting with '%c' will be ignored.\n");
> > +
> > static const char merge_editor_comment[] =
> > N_("Please enter a commit message to explain why this merge is necessary,\n"
> > "especially if it merges an updated upstream into a topic branch.\n"
> > "\n"
> > - "Lines starting with '%c' will be ignored, and an empty message aborts\n"
> > - "the commit.\n");
> > + "An empty message aborts the commit.\n");
> > static void write_merge_heads(struct commit_list *);
> > static void prepare_to_commit(struct commit_list *remoteheads)
> > {
> > struct strbuf msg = STRBUF_INIT;
> > strbuf_addbuf(&msg, &merge_msg);
> > - strbuf_addch(&msg, '\n');
> > if (squash)
> > BUG("the control must not reach here under --squash");
> > - if (0 < option_edit)
> > - strbuf_commented_addf(&msg, _(merge_editor_comment), comment_line_char);
> > + if (0 < option_edit) {
> > + strbuf_addch(&msg, '\n');
> > + if (cleanup_mode == COMMIT_MSG_CLEANUP_SCISSORS)
> > + wt_status_append_cut_line(&msg);
> > + else
> > + strbuf_commented_addf(&msg, _(comment_line_explanation), comment_line_char);
> > +
> > + strbuf_commented_addf(&msg, "\n");
> > + strbuf_commented_addf(&msg, _(merge_editor_comment));
> > + }
>
> This still changes the wording of the message cf https://public-inbox.org/git/cover.1552275703.git.liu.denton@gmail.com/T/#m09cb1a05eb3bffb47ee9f25572904a7279efa362
Will do.
Thanks again for reviewing carefully!
>
> Best Wishes
>
> Phillip
>
> > if (signoff)
> > append_signoff(&msg, ignore_non_trailer(msg.buf, msg.len), 0);
> > write_merge_heads(remoteheads);
> > @@ -832,7 +848,7 @@ static void prepare_to_commit(struct commit_list *remoteheads)
> > abort_commit(remoteheads, NULL);
> > read_merge_msg(&msg);
> > - strbuf_stripspace(&msg, 0 < option_edit);
> > + cleanup_message(&msg, cleanup_mode, 0);
> > if (!msg.len)
> > abort_commit(remoteheads, _("Empty commit message."));
> > strbuf_release(&merge_msg);
> > @@ -880,7 +896,6 @@ static int finish_automerge(struct commit *head,
> > parents = remoteheads;
> > if (!head_subsumed || fast_forward == FF_NO)
> > commit_list_insert(head, &parents);
> > - strbuf_addch(&merge_msg, '\n');
> > prepare_to_commit(remoteheads);
> > if (commit_tree(merge_msg.buf, merge_msg.len, result_tree, parents,
> > &result_commit, NULL, sign_commit))
> > @@ -1389,6 +1404,8 @@ int cmd_merge(int argc, const char **argv, const char *prefix)
> > if (option_edit < 0)
> > option_edit = default_edit_option();
> > + cleanup_mode = get_cleanup_mode(cleanup_arg, 0 < option_edit, 1);
> > +
> > if (!use_strategies) {
> > if (!remoteheads)
> > ; /* already up-to-date */
> > diff --git a/builtin/pull.c b/builtin/pull.c
> > index 33db889955..292c1dac27 100644
> > --- a/builtin/pull.c
> > +++ b/builtin/pull.c
> > @@ -101,6 +101,7 @@ static char *opt_signoff;
> > static char *opt_squash;
> > static char *opt_commit;
> > static char *opt_edit;
> > +static char *opt_cleanup;
> > static char *opt_ff;
> > static char *opt_verify_signatures;
> > static int opt_autostash = -1;
> > @@ -168,6 +169,9 @@ static struct option pull_options[] = {
> > OPT_PASSTHRU(0, "edit", &opt_edit, NULL,
> > N_("edit message before committing"),
> > PARSE_OPT_NOARG),
> > + OPT_PASSTHRU(0, "cleanup", &opt_cleanup, NULL,
> > + N_("how to strip spaces and #comments from message"),
> > + 0),
> > OPT_PASSTHRU(0, "ff", &opt_ff, NULL,
> > N_("allow fast-forward"),
> > PARSE_OPT_NOARG),
> > @@ -644,6 +648,8 @@ static int run_merge(void)
> > argv_array_push(&args, opt_commit);
> > if (opt_edit)
> > argv_array_push(&args, opt_edit);
> > + if (opt_cleanup)
> > + argv_array_push(&args, opt_cleanup);
> > if (opt_ff)
> > argv_array_push(&args, opt_ff);
> > if (opt_verify_signatures)
> > diff --git a/t/t7604-merge-custom-message.sh b/t/t7604-merge-custom-message.sh
> > index b045fdb413..c9685a318d 100755
> > --- a/t/t7604-merge-custom-message.sh
> > +++ b/t/t7604-merge-custom-message.sh
> > @@ -51,4 +51,71 @@ test_expect_success 'merge --log appends to custom message' '
> > test_cmp exp.log actual
> > '
> > +mesg_with_comment_and_newlines='
> > +# text
> > +
> > +'
> > +
> > +test_expect_success 'prepare file with comment line and trailing newlines' '
> > + printf "%s" "$mesg_with_comment_and_newlines" >expect
> > +'
> > +
> > +test_expect_success 'cleanup commit messages (verbatim option)' '
> > + git reset --hard c1 &&
> > + git merge --cleanup=verbatim -F expect c2 &&
> > + git cat-file commit HEAD >actual &&
> > + sed -e "1,/^$/d" <actual >tmp &&
> > + mv tmp actual &&
> > + test_cmp expect actual
> > +'
> > +
> > +test_expect_success 'cleanup commit messages (whitespace option)' '
> > + git reset --hard c1 &&
> > + test_write_lines "" "# text" "" >text &&
> > + echo "# text" >expect &&
> > + git merge --cleanup=whitespace -F text c2 &&
> > + git cat-file commit HEAD >actual &&
> > + sed -e "1,/^$/d" <actual >tmp &&
> > + mv tmp actual &&
> > + test_cmp expect actual
> > +'
> > +
> > +test_expect_success 'cleanup merge messages (scissors option)' '
> > + git reset --hard c1 &&
> > + cat >text <<-\EOF &&
> > +
> > + # to be kept
> > +
> > + # ------------------------ >8 ------------------------
> > + # to be kept, too
> > + # ------------------------ >8 ------------------------
> > + to be removed
> > + # ------------------------ >8 ------------------------
> > + to be removed, too
> > + EOF
> > +
> > + cat >expect <<-\EOF &&
> > + # to be kept
> > +
> > + # ------------------------ >8 ------------------------
> > + # to be kept, too
> > + EOF
> > + git merge --cleanup=scissors -e -F text c2 &&
> > + git cat-file commit HEAD >actual &&
> > + sed -e "1,/^$/d" <actual >tmp &&
> > + mv tmp actual &&
> > + test_cmp expect actual
> > +'
> > +
> > +test_expect_success 'cleanup commit messages (strip option)' '
> > + git reset --hard c1 &&
> > + test_write_lines "" "# text" "sample" "" >text &&
> > + echo sample >expect &&
> > + git merge --cleanup=strip -F text c2 &&
> > + git cat-file commit HEAD >actual &&
> > + sed -e "1,/^$/d" <actual >tmp &&
> > + mv tmp actual &&
> > + test_cmp expect actual
> > +'
> > +
> > test_done
> > diff --git a/wt-status.c b/wt-status.c
> > index 445a36204a..b81fcd428d 100644
> > --- a/wt-status.c
> > +++ b/wt-status.c
> > @@ -1006,13 +1006,19 @@ size_t wt_status_locate_end(const char *s, size_t len)
> > return len;
> > }
> > -void wt_status_add_cut_line(FILE *fp)
> > +void wt_status_append_cut_line(struct strbuf *buf)
> > {
> > const char *explanation = _("Do not modify or remove the line above.\nEverything below it will be ignored.");
> > +
> > + strbuf_commented_addf(buf, "%s", cut_line);
> > + strbuf_add_commented_lines(buf, explanation, strlen(explanation));
> > +}
> > +
> > +void wt_status_add_cut_line(FILE *fp)
> > +{
> > struct strbuf buf = STRBUF_INIT;
> > - fprintf(fp, "%c %s", comment_line_char, cut_line);
> > - strbuf_add_commented_lines(&buf, explanation, strlen(explanation));
> > + wt_status_append_cut_line(&buf);
> > fputs(buf.buf, fp);
> > strbuf_release(&buf);
> > }
> > diff --git a/wt-status.h b/wt-status.h
> > index 3a95975032..64f1ddc9fd 100644
> > --- a/wt-status.h
> > +++ b/wt-status.h
> > @@ -129,6 +129,7 @@ struct wt_status {
> > };
> > size_t wt_status_locate_end(const char *s, size_t len);
> > +void wt_status_append_cut_line(struct strbuf *buf);
> > void wt_status_add_cut_line(FILE *fp);
> > void wt_status_prepare(struct repository *r, struct wt_status *s);
> > void wt_status_print(struct wt_status *s);
> >
next prev parent reply other threads:[~2019-03-20 6:32 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 5:24 [RFC PATCH 0/2] Fix scissors bug during merge conflict Denton Liu
2018-11-14 5:24 ` [RFC PATCH 1/2] commit: don't add scissors line if one exists Denton Liu
2018-11-14 8:06 ` Junio C Hamano
2018-11-14 18:06 ` Denton Liu
2018-11-16 3:32 ` Junio C Hamano
2018-11-14 5:25 ` [RFC PATCH 2/2] merge: add scissors line on merge conflict Denton Liu
2018-11-14 7:52 ` [RFC PATCH 0/2] Fix scissors bug during " Junio C Hamano
2018-11-14 8:10 ` Denton Liu
2018-11-16 15:19 ` [PATCH v2 " Denton Liu
2018-11-16 15:20 ` [PATCH v2 2/2] merge: add scissors line on " Denton Liu
2018-11-17 23:32 ` [PATCH v3 0/1] Fix scissors bug during " Denton Liu
2018-11-17 23:32 ` [PATCH v3 1/1] merge: add scissors line on " Denton Liu
2018-11-18 14:18 ` SZEDER Gábor
2018-11-18 6:54 ` [PATCH v3 0/1] Fix scissors bug during " Junio C Hamano
2018-11-21 3:13 ` [PATCH v4 0/2] " Denton Liu
2018-11-21 3:13 ` [PATCH v4 1/2] t7600: clean up 'merge --squash c3 with c7' test Denton Liu
2018-11-21 3:13 ` [PATCH v4 2/2] merge: add scissors line on merge conflict Denton Liu
2018-11-21 9:38 ` [PATCH v4 0/2] Fix scissors bug during " Junio C Hamano
2018-11-22 1:10 ` Denton Liu
2018-11-24 2:05 ` Junio C Hamano
2018-12-25 13:55 ` [PATCH v5 0/4] Add git-merge --cleanup support Denton Liu
2018-12-25 13:55 ` [PATCH v5 1/4] commit: extract cleanup_mode functions to sequencer Denton Liu
2018-12-25 13:56 ` [PATCH v5 2/4] t7600: clean up 'merge --squash c3 with c7' test Denton Liu
2018-12-25 13:56 ` [PATCH v5 3/4] merge: cleanup messages like commit Denton Liu
2018-12-25 13:56 ` [PATCH v5 4/4] merge: add scissors line on merge conflict Denton Liu
2019-01-23 5:06 ` [PATCH v6 0/4] Add git-merge --cleanup support Denton Liu
2019-01-23 5:06 ` [PATCH v6 1/4] commit: extract cleanup_mode functions to sequencer Denton Liu
2019-01-23 5:06 ` [PATCH v6 2/4] t7600: clean up 'merge --squash c3 with c7' test Denton Liu
2019-01-23 5:06 ` [PATCH v6 3/4] merge: cleanup messages like commit Denton Liu
2019-01-23 5:06 ` [PATCH v6 4/4] merge: add scissors line on merge conflict Denton Liu
2019-03-11 3:42 ` [PATCH v7 0/8] Fix scissors bug during conflict Denton Liu
2019-03-11 3:42 ` [PATCH v7 1/8] t7600: clean up 'merge --squash c3 with c7' test Denton Liu
2019-03-12 1:03 ` Junio C Hamano
2019-03-11 3:42 ` [PATCH v7 2/8] t3507: cleanup space after redirection operators Denton Liu
2019-03-11 3:42 ` [PATCH v7 3/8] commit: extract cleanup_mode functions to sequencer Denton Liu
2019-03-11 3:42 ` [PATCH v7 4/8] sequencer.c: remove duplicate code Denton Liu
2019-03-11 16:45 ` Phillip Wood
2019-03-11 3:42 ` [PATCH v7 5/8] merge: cleanup messages like commit Denton Liu
2019-03-11 5:49 ` Eric Sunshine
2019-03-11 10:14 ` Phillip Wood
2019-03-11 17:00 ` Eric Sunshine
2019-03-11 16:58 ` Phillip Wood
2019-03-12 5:50 ` Junio C Hamano
2019-03-11 3:42 ` [PATCH v7 6/8] merge: add scissors line on merge conflict Denton Liu
2019-03-11 5:55 ` Eric Sunshine
2019-03-11 3:42 ` [PATCH v7 7/8] sequencer.c: define get_config_from_cleanup Denton Liu
2019-03-11 6:19 ` Eric Sunshine
2019-03-12 6:29 ` Junio C Hamano
2019-03-11 3:42 ` [PATCH v7 8/8] cherry-pick/revert: add scissors line on merge conflict Denton Liu
2019-03-12 11:11 ` Phillip Wood
2019-03-11 6:44 ` [PATCH v7 0/8] Fix scissors bug during conflict Junio C Hamano
2019-03-17 10:15 ` [PATCH v8 00/11] " Denton Liu
2019-03-17 10:15 ` [PATCH v8 01/11] t7600: clean up style Denton Liu
2019-03-17 10:15 ` [PATCH v8 02/11] t3507: cleanup space after redirection operators Denton Liu
2019-03-17 10:15 ` [PATCH v8 03/11] t7604: refactor out Git commands upstream of pipe Denton Liu
2019-03-17 10:16 ` [PATCH v8 04/11] t7502: clean up test style Denton Liu
2019-03-17 10:16 ` [PATCH v8 05/11] commit: extract cleanup_mode functions to sequencer Denton Liu
2019-03-17 10:16 ` [PATCH v8 06/11] parse-options.h: extract common --cleanup option Denton Liu
2019-03-17 10:16 ` [PATCH v8 07/11] sequencer.c: remove duplicate code Denton Liu
2019-03-17 10:16 ` [PATCH v8 08/11] merge: cleanup messages like commit Denton Liu
2019-03-19 11:13 ` Phillip Wood
2019-03-20 6:32 ` Denton Liu [this message]
2019-03-17 10:16 ` [PATCH v8 09/11] merge: add scissors line on merge conflict Denton Liu
2019-03-17 10:16 ` [PATCH v8 10/11] sequencer.c: define describe_cleanup_mode Denton Liu
2019-03-18 20:04 ` Eric Sunshine
2019-03-18 20:30 ` Denton Liu
2019-03-18 20:32 ` Eric Sunshine
2019-03-19 0:55 ` Ramsay Jones
2019-03-17 10:16 ` [PATCH v8 11/11] cherry-pick/revert: add scissors line on merge conflict Denton Liu
2019-03-17 13:05 ` [PATCH v8 00/11] Fix scissors bug during conflict SZEDER Gábor
2019-03-18 3:02 ` Denton Liu
2019-03-18 6:35 ` Junio C Hamano
2019-03-18 8:03 ` Denton Liu
2019-03-18 8:25 ` Junio C Hamano
2019-03-21 6:53 ` [PATCH v9 " Denton Liu
2019-03-21 6:53 ` [PATCH v9 01/11] t7600: clean up style Denton Liu
2019-03-21 6:53 ` [PATCH v9 02/11] t3507: " Denton Liu
2019-03-21 6:53 ` [PATCH v9 03/11] t7604: " Denton Liu
2019-03-21 6:53 ` [PATCH v9 04/11] t7502: " Denton Liu
2019-03-21 6:53 ` [PATCH v9 05/11] commit: extract cleanup_mode functions to sequencer Denton Liu
2019-03-21 6:53 ` [PATCH v9 06/11] parse-options.h: extract common --cleanup option Denton Liu
2019-03-21 6:53 ` [PATCH v9 07/11] sequencer.c: remove duplicate code Denton Liu
2019-03-26 10:44 ` Phillip Wood
2019-03-21 6:53 ` [PATCH v9 08/11] merge: cleanup messages like commit Denton Liu
2019-03-21 6:53 ` [PATCH v9 09/11] merge: add scissors line on merge conflict Denton Liu
2019-03-21 6:54 ` [PATCH v9 10/11] sequencer.c: define describe_cleanup_mode Denton Liu
2019-03-21 6:54 ` [PATCH v9 11/11] cherry-pick/revert: add scissors line on merge conflict Denton Liu
2019-04-17 10:23 ` [PATCH v10 00/10] Fix scissors bug during conflict Phillip Wood
2019-04-17 10:23 ` [PATCH v10 01/10] t7600: clean up style Phillip Wood
2019-04-17 10:23 ` [PATCH v10 02/10] t3507: " Phillip Wood
2019-04-17 10:23 ` [PATCH v10 03/10] t7604: " Phillip Wood
2019-04-17 10:23 ` [PATCH v10 04/10] t7502: " Phillip Wood
2019-04-17 10:23 ` [PATCH v10 05/10] commit: extract cleanup_mode functions to sequencer Phillip Wood
2019-04-17 10:23 ` [PATCH v10 06/10] parse-options.h: extract common --cleanup option Phillip Wood
2019-04-17 10:23 ` [PATCH v10 07/10] merge: cleanup messages like commit Phillip Wood
2019-04-17 10:23 ` [PATCH v10 08/10] merge: add scissors line on merge conflict Phillip Wood
2019-04-17 10:23 ` [PATCH v10 09/10] sequencer.c: save and restore cleanup mode Phillip Wood
2019-04-17 17:02 ` Denton Liu
2019-04-17 19:53 ` Phillip Wood
2019-04-18 17:21 ` Denton Liu
2019-04-17 10:23 ` [PATCH v10 10/10] cherry-pick/revert: add scissors line on merge conflict Phillip Wood
2019-04-18 5:19 ` [PATCH v10 00/10] Fix scissors bug during conflict Junio C Hamano
2019-04-18 9:14 ` Phillip Wood
[not found] ` <cover.1542380865.git.liu.denton@gmail.com>
2018-11-16 15:19 ` [PATCH v2 1/2] commit: don't add scissors line if one exists in MERGE_MSG Denton Liu
2018-11-17 8:06 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190320063215.GA9432@archbookpro.localdomain \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ramsay@ramsayjones.plus.com \
--cc=sunshine@sunshineco.com \
--cc=szeder.dev@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).