From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Stefan Beller" <sbeller@google.com>
Subject: Re: [RFC PATCH 5/5] format-patch: add --creation-weight tweak for --range-diff
Date: Tue, 17 Jul 2018 13:00:25 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1807171259290.71@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20180530080325.37520-6-sunshine@sunshineco.com>
Hi Eric,
On Wed, 30 May 2018, Eric Sunshine wrote:
> When generating a range-diff, matching up commits between two version of
> a patch series involves heuristics, thus may give unexpected results.
> git-branch-diff allows tweaking the heuristic via --creation-weight.
> Follow suit by accepting --creation-weight in combination with
> --range-diff when generating a range-diff for a cover-letter.
Since I opted to change this to `--creation-factor`, taking an integer
between 0 and 100 (essentially), this patch will need heavy adjustment ;-=)
Thanks,
Dscho
> Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
> ---
> Documentation/git-format-patch.txt | 8 +++++++-
> builtin/log.c | 19 +++++++++++++++----
> 2 files changed, 22 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
> index 25026ae26e..7ed9ec9dae 100644
> --- a/Documentation/git-format-patch.txt
> +++ b/Documentation/git-format-patch.txt
> @@ -23,7 +23,7 @@ SYNOPSIS
> [(--reroll-count|-v) <n>]
> [--to=<email>] [--cc=<email>]
> [--[no-]cover-letter] [--quiet] [--notes[=<ref>]]
> - [--range-diff=<previous>]
> + [--range-diff=<previous> [--creation-weight=<factor>]]
> [--progress]
> [<common diff options>]
> [ <since> | <revision range> ]
> @@ -240,6 +240,12 @@ feeding the result to `git send-email`.
> disjoint (for example `git format-patch --cover-letter
> --range-diff=feature/v1~3..feature/v1 -3 feature/v2`).
>
> +--creation-weight=<factor>::
> + Used with `--range-diff`, tweak the heuristic which matches up commits
> + between the previous and current series of patches by adjusting the
> + creation/deletion cost fudge factor. See linkgit:git-branch-diff[1])
> + for details.
> +
> --notes[=<ref>]::
> Append the notes (see linkgit:git-notes[1]) for the commit
> after the three-dash line.
> diff --git a/builtin/log.c b/builtin/log.c
> index 3089d3a50a..2c49011b51 100644
> --- a/builtin/log.c
> +++ b/builtin/log.c
> @@ -1012,12 +1012,16 @@ static void infer_diff_ranges(struct argv_array *args,
> }
>
> static int get_range_diff(struct strbuf *sb,
> - const struct argv_array *ranges)
> + const struct argv_array *ranges,
> + const char *creation_weight)
> {
> struct child_process cp = CHILD_PROCESS_INIT;
>
> cp.git_cmd = 1;
> argv_array_pushl(&cp.args, "branch-diff", "--no-color", NULL);
> + if (creation_weight)
> + argv_array_pushf(&cp.args,
> + "--creation-weight=%s", creation_weight);
> argv_array_pushv(&cp.args, ranges->argv);
> return capture_command(&cp, sb, 0);
> }
> @@ -1047,7 +1051,8 @@ static void make_cover_letter(struct rev_info *rev, int use_stdout,
> int nr, struct commit **list,
> const char *branch_name,
> int quiet,
> - const char *range_diff)
> + const char *range_diff,
> + const char *creation_weight)
> {
> const char *committer;
> const char *body = "*** SUBJECT HERE ***\n\n*** BLURB HERE ***\n";
> @@ -1070,7 +1075,7 @@ static void make_cover_letter(struct rev_info *rev, int use_stdout,
> if (range_diff) {
> struct argv_array ranges = ARGV_ARRAY_INIT;
> infer_diff_ranges(&ranges, range_diff, origin, head);
> - if (get_range_diff(&diff, &ranges))
> + if (get_range_diff(&diff, &ranges, creation_weight))
> die(_("failed to generate range-diff"));
> argv_array_clear(&ranges);
> }
> @@ -1495,6 +1500,7 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
> int show_progress = 0;
> struct progress *progress = NULL;
> const char *range_diff = NULL;
> + const char *creation_weight = NULL;
>
> const struct option builtin_format_patch_options[] = {
> { OPTION_CALLBACK, 'n', "numbered", &numbered, NULL,
> @@ -1570,6 +1576,8 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
> N_("show progress while generating patches")),
> OPT_STRING(0, "range-diff", &range_diff, N_("rev-range"),
> N_("show changes against <rev-range> in cover letter")),
> + OPT_STRING(0, "creation-weight", &creation_weight, N_("factor"),
> + N_("fudge factor by which creation is weighted")),
> OPT_END()
> };
>
> @@ -1664,6 +1672,9 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
> die (_("--subject-prefix/--rfc and -k are mutually exclusive."));
> rev.preserve_subject = keep_subject;
>
> + if (creation_weight && !range_diff)
> + die(_("--creation-weight requires --range-diff"));
> +
> argc = setup_revisions(argc, argv, &rev, &s_r_opt);
> if (argc > 1)
> die (_("unrecognized argument: %s"), argv[1]);
> @@ -1827,7 +1838,7 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
> gen_message_id(&rev, "cover");
> make_cover_letter(&rev, use_stdout,
> origin, nr, list, branch_name, quiet,
> - range_diff);
> + range_diff, creation_weight);
> print_bases(&bases, rev.diffopt.file);
> print_signature(rev.diffopt.file);
> total++;
> --
> 2.17.1.1235.ge295dfb56e
>
>
next prev parent reply other threads:[~2018-07-17 11:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 8:03 [RFC PATCH 0/5] format-patch: automate cover letter range-diff Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 1/5] format-patch: allow additional generated content in make_cover_letter() Eric Sunshine
2018-07-17 10:15 ` Johannes Schindelin
2018-07-17 10:24 ` Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 2/5] format-patch: add --range-diff option to embed diff in cover letter Eric Sunshine
2018-07-17 10:30 ` Johannes Schindelin
2018-07-17 10:49 ` Eric Sunshine
2018-07-26 10:55 ` Johannes Schindelin
2018-07-26 20:57 ` Eric Sunshine
2018-07-27 15:18 ` Johannes Schindelin
2018-05-30 8:03 ` [RFC PATCH 3/5] format-patch: extend --range-diff to accept revision range Eric Sunshine
2018-05-30 18:58 ` Stefan Beller
2018-05-30 20:26 ` Eric Sunshine
2018-07-17 10:44 ` Johannes Schindelin
2018-07-17 10:50 ` Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 4/5] format-patch: teach --range-diff to respect -v/--reroll-count Eric Sunshine
2018-05-30 19:03 ` Stefan Beller
2018-05-30 20:44 ` Eric Sunshine
2018-05-30 21:03 ` Stefan Beller
2018-05-30 21:14 ` Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 5/5] format-patch: add --creation-weight tweak for --range-diff Eric Sunshine
2018-07-17 11:00 ` Johannes Schindelin [this message]
2018-05-30 9:25 ` [RFC PATCH 0/5] format-patch: automate cover letter range-diff Ævar Arnfjörð Bjarmason
2018-06-06 19:16 ` Duy Nguyen
2018-06-07 8:34 ` Eric Sunshine
2018-06-07 15:09 ` Duy Nguyen
2018-07-17 10:04 ` Johannes Schindelin
2018-07-26 12:03 ` Andrei Rybak
2018-07-26 15:57 ` Johannes Schindelin
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=nycvar.QRO.7.76.6.1807171259290.71@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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).