From: "ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Denton Liu <liu.denton@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
ZheNing Hu <adlternative@gmail.com>,
ZheNing Hu <adlternative@gmail.com>
Subject: [PATCH] [GSOC][RFC] format-patch: pass --right-only to range-diff
Date: Sun, 07 Mar 2021 06:57:19 +0000 [thread overview]
Message-ID: <pull.898.git.1615100240295.gitgitgadget@gmail.com> (raw)
From: ZheNing Hu <adlternative@gmail.com>
In https://lore.kernel.org/git/YBx5rmVsg1LJhSKN@nand.local/,
Taylor Blau proposing 'git format-patch --cover-letter
--range-diff' may mistakenly place upstream commit in the
range-diff output. Teach `format-patch` pass `--right-only`
to range-diff, maybe can avoid this kind of mistake.
Because `git rebase --apply` will internally call `git
format-patch -k --stdout --full-index --cherry-pick --right-only
--src-prefix=a/ --dst-prefix=b/ --no-renames --no-cover-letter
--pretty=mboxrd --topo-order --no-base`, In order to avoid the
ambiguity of `--right-only`, users can call `format-patch
--range-diff --only-right` instead of `--right-only` to only emit
output related to the second range.
Signed-off-by: ZheNing Hu <adlternative@gmail.com>
---
[GSOC][RFC] format-patch: pass --right-only to range-diff
Transfer parameters are relatively simple. But because I can' t
reproduce the situation, There's no big difference between adding
---only-right and not adding ---only-right. So I haven't written the
test files for the time being.
I may need to ask reviewers opinion first.
this want to fix #876 Thanks.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-898%2Fadlternative%2Fformat-patch-range-diff-right-only-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-898/adlternative/format-patch-range-diff-right-only-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/898
Documentation/git-format-patch.txt | 5 ++++-
builtin/log.c | 15 ++++++++++-----
2 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index 3e49bf221087..5dae34c3090b 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -27,7 +27,7 @@ SYNOPSIS
[--[no-]encode-email-headers]
[--no-notes | --notes[=<ref>]]
[--interdiff=<previous>]
- [--range-diff=<previous> [--creation-factor=<percent>]]
+ [--range-diff=<previous> [--creation-factor=<percent>] [--right-only]]
[--filename-max-length=<n>]
[--progress]
[<common diff options>]
@@ -301,6 +301,9 @@ material (this may change in the future).
creation/deletion cost fudge factor. See linkgit:git-range-diff[1])
for details.
+--only-right:
+ Used with `--range-diff`, only emit output related to the second range.
+
--notes[=<ref>]::
--no-notes::
Append the notes (see linkgit:git-notes[1]) for the commit
diff --git a/builtin/log.c b/builtin/log.c
index f67b67d80ed1..5d2f39fd19a7 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -1153,7 +1153,7 @@ static void make_cover_letter(struct rev_info *rev, int use_separate_file,
struct commit *origin,
int nr, struct commit **list,
const char *branch_name,
- int quiet)
+ int quiet, int right_only)
{
const char *committer;
struct shortlog log;
@@ -1228,7 +1228,8 @@ static void make_cover_letter(struct rev_info *rev, int use_separate_file,
.creation_factor = rev->creation_factor,
.dual_color = 1,
.diffopt = &opts,
- .other_arg = &other_arg
+ .other_arg = &other_arg,
+ .right_only = right_only
};
diff_setup(&opts);
@@ -1732,7 +1733,7 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
struct strbuf rdiff2 = STRBUF_INIT;
struct strbuf rdiff_title = STRBUF_INIT;
int creation_factor = -1;
-
+ int right_only = 0;
const struct option builtin_format_patch_options[] = {
OPT_CALLBACK_F('n', "numbered", &numbered, NULL,
N_("use [PATCH n/m] even with a single patch"),
@@ -1814,6 +1815,8 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
parse_opt_object_name),
OPT_STRING(0, "range-diff", &rdiff_prev, N_("refspec"),
N_("show changes against <refspec> in cover letter or single patch")),
+ OPT_BOOL(0, "only-right", &right_only,
+ N_("only emit output related to the second range")),
OPT_INTEGER(0, "creation-factor", &creation_factor,
N_("percentage by which creation is weighted")),
OPT_END()
@@ -2087,7 +2090,8 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
creation_factor = RANGE_DIFF_CREATION_FACTOR_DEFAULT;
else if (!rdiff_prev)
die(_("--creation-factor requires --range-diff"));
-
+ if (right_only && !rdiff_prev)
+ die(_("--right_only requires --range-diff"));
if (rdiff_prev) {
if (!cover_letter && total != 1)
die(_("--range-diff requires --cover-letter or single patch"));
@@ -2134,7 +2138,8 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
if (thread)
gen_message_id(&rev, "cover");
make_cover_letter(&rev, !!output_directory,
- origin, nr, list, branch_name, quiet);
+ origin, nr, list, branch_name, quiet,
+ right_only);
print_bases(&bases, rev.diffopt.file);
print_signature(rev.diffopt.file);
total++;
base-commit: be7935ed8bff19f481b033d0d242c5d5f239ed50
--
gitgitgadget
next reply other threads:[~2021-03-07 6:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 6:57 ZheNing Hu via GitGitGadget [this message]
2021-03-08 20:18 ` [PATCH] [GSOC][RFC] format-patch: pass --right-only to range-diff Taylor Blau
2021-03-09 7:28 ` ZheNing Hu
2021-03-12 21:55 ` Junio C Hamano
2021-03-12 22:09 ` Junio C Hamano
2021-03-09 8:33 ` [PATCH v2] [GSOC][RFC] format-patch: pass --left-only " ZheNing Hu via GitGitGadget
2021-03-09 9:00 ` Eric Sunshine
2021-03-09 9:35 ` ZheNing Hu
2021-03-09 10:28 ` [PATCH v3] " ZheNing Hu via GitGitGadget
2021-03-12 22:50 ` Junio C Hamano
2021-03-13 4:01 ` ZheNing Hu
2021-03-13 23:23 ` Junio C Hamano
2021-03-14 2:16 ` ZheNing Hu
2021-03-14 2:37 ` ZheNing Hu
2021-03-14 2:41 ` ZheNing Hu
2021-03-14 8:10 ` [PATCH v4] [GSOC] " ZheNing Hu via GitGitGadget
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=pull.898.git.1615100240295.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=adlternative@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=liu.denton@gmail.com \
--cc=me@ttaylorr.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).