From: Junio C Hamano <gitster@pobox.com>
To: "ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>,
ZheNing Hu <adlternative@gmail.com>
Subject: Re: [PATCH v2] format-patch: allow a non-integral version numbers
Date: Tue, 02 Mar 2021 19:44:42 -0800 [thread overview]
Message-ID: <xmqqzgzklx3p.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: pull.885.v2.git.1614588030233.gitgitgadget@gmail.com
"ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com> writes:
> diff --git a/builtin/log.c b/builtin/log.c
> index f67b67d80ed1..95c95eab5393 100644
> --- a/builtin/log.c
> +++ b/builtin/log.c
> @@ -1662,13 +1662,15 @@ static void print_bases(struct base_tree_info *bases, FILE *file)
> oidclr(&bases->base_commit);
> }
>
> -static const char *diff_title(struct strbuf *sb, int reroll_count,
> - const char *generic, const char *rerolled)
> +static const char *diff_title(struct strbuf *sb, const char *reroll_count, int reroll_count_is_integer,
> + const char*previous_count, const char *generic, const char *rerolled)
Avoid overly long lines here, but quite honestly, I find that this
interface is way too ugly to live.
Can we do all the computation around previous count in the caller,
so that this function only takes reroll_count and previous_count
that are both "const char *", and then the body will just be:
if (!reroll_count)
strbuf_addstr(sb, generic);
else if (previous_count)
strbuf_addf(sb, rerolled, previous_count);
return sb->buf;
That way, the callers do not have to prepare two different rerolled
template and switch between them based on "is_integer".
In other words, they need to care "is_integer" already, so making
them responsible for preparing "previous_count" always usable by
this function would be a reasonable way to partition the tasks
between this callee and the caller.
That way, this function do not even need to know about "is_integer"
bit.
> + if (previous_count && !reroll_count)
> + usage(_("previous-count can only used when reroll-count is used"));
> + if (reroll_count) {
> struct strbuf sprefix = STRBUF_INIT;
> - strbuf_addf(&sprefix, "%s v%d",
> + char ch;
> + size_t i = 0 , reroll_count_len = strlen(reroll_count);
> +
> + for (; i != reroll_count_len; i++) {
> + ch = reroll_count[i];
> + if(!isdigit(ch))
> + break;
> + }
> + reroll_count_is_integer = i == reroll_count_len ? 1 : 0;
Do not reinvent integer parsing. In our codebase, it is far more
common (and it is less error prone) to do something like this:
char *endp;
count = strtoul(reroll_count_string, &endp, 10);
if (*endp) {
/* followed by non-digit: not an integer */
is_integer = 0;
} else {
is_integer = 1;
if (0 < count)
previous_count_string = xstrfmt("%d", count - 1);
}
And then, you can move the "if previous is there and count is not
specified" check after this block, to make sure that a non-integer
reroll count is always accompanied by a previous count, for example.
> + strbuf_addf(&sprefix, "%s v%s",
> rev.subject_prefix, reroll_count);
> rev.reroll_count = reroll_count;
> rev.subject_prefix = strbuf_detach(&sprefix, NULL);
> @@ -2079,8 +2095,9 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
> rev.idiff_oid1 = &idiff_prev.oid[idiff_prev.nr - 1];
> rev.idiff_oid2 = get_commit_tree_oid(list[0]);
> rev.idiff_title = diff_title(&idiff_title, reroll_count,
> - _("Interdiff:"),
> - _("Interdiff against v%d:"));
> + reroll_count_is_integer, previous_count, _("Interdiff:"),
> + reroll_count_is_integer ? _("Interdiff against v%d:") :
> + _("Interdiff against v%s:"));
I've touched the calling convention into diff_title() function
earlier.
> @@ -2098,8 +2115,9 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
> rev.rdiff2 = rdiff2.buf;
> rev.creation_factor = creation_factor;
> rev.rdiff_title = diff_title(&rdiff_title, reroll_count,
> - _("Range-diff:"),
> - _("Range-diff against v%d:"));
> + reroll_count_is_integer, previous_count, _("Range-diff:"),
> + reroll_count_is_integer ? _("Range-diff against v%d:") :
> + _("Range-diff against v%s:"));
Ditto.
next prev parent reply other threads:[~2021-03-03 14:21 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 16:15 [PATCH] format-patch: allow a non-integral version numbers ZheNing Hu via GitGitGadget
2021-02-25 17:56 ` Eric Sunshine
2021-02-27 7:00 ` ZheNing Hu
2021-02-25 18:13 ` Junio C Hamano
2021-02-27 7:30 ` ZheNing Hu
2021-03-17 11:46 ` Đoàn Trần Công Danh
2021-03-17 19:17 ` Junio C Hamano
2021-03-01 8:40 ` [PATCH v2] " ZheNing Hu via GitGitGadget
2021-03-03 3:44 ` Junio C Hamano [this message]
2021-03-03 9:02 ` Denton Liu
2021-03-04 0:54 ` Junio C Hamano
2021-03-04 2:08 ` ZheNing Hu
2021-03-04 3:27 ` Eric Sunshine
2021-03-04 8:41 ` Denton Liu
2021-03-04 12:12 ` [PATCH v3] " ZheNing Hu via GitGitGadget
2021-03-04 12:49 ` Denton Liu
2021-03-05 4:56 ` ZheNing Hu
2021-03-05 7:10 ` [PATCH v4] " ZheNing Hu via GitGitGadget
2021-03-15 23:41 ` Eric Sunshine
2021-03-16 5:48 ` ZheNing Hu
2021-03-16 6:15 ` Eric Sunshine
2021-03-17 17:27 ` Junio C Hamano
2021-03-16 8:25 ` [PATCH v5] " ZheNing Hu via GitGitGadget
2021-03-16 23:36 ` Eric Sunshine
2021-03-17 2:05 ` ZheNing Hu
2021-03-18 6:00 ` [PATCH v6] " ZheNing Hu via GitGitGadget
2021-03-19 6:00 ` Eric Sunshine
2021-03-19 7:25 ` ZheNing Hu
2021-03-19 11:21 ` [PATCH v7] " ZheNing Hu via GitGitGadget
2021-03-19 16:01 ` Junio C Hamano
2021-03-20 3:08 ` ZheNing Hu
2021-03-19 17:28 ` Junio C Hamano
2021-03-20 3:04 ` ZheNing Hu
2021-03-20 14:56 ` [PATCH v8] " ZheNing Hu via GitGitGadget
2021-03-20 19:55 ` Junio C Hamano
2021-03-21 2:45 ` ZheNing Hu
2021-03-21 4:05 ` Eric Sunshine
2021-03-21 5:45 ` Junio C Hamano
2021-03-21 5:54 ` Eric Sunshine
2021-03-24 8:46 ` Denton Liu
2021-03-21 7:22 ` ZheNing Hu
2021-03-21 9:00 ` [PATCH v9] " ZheNing Hu via GitGitGadget
2021-03-23 5:31 ` Eric Sunshine
2021-03-23 6:42 ` Junio C Hamano
2021-03-23 8:53 ` ZheNing Hu
2021-03-23 9:16 ` ZheNing Hu
2021-03-23 11:12 ` [PATCH v10] " ZheNing Hu via GitGitGadget
2021-03-24 3:58 ` Eric Sunshine
2021-03-24 4:43 ` ZheNing Hu
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=xmqqzgzklx3p.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=adlternative@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=liu.denton@gmail.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).