From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Eli Schwartz <eschwartz@archlinux.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 3/3] pretty: add abbrev option to %(describe)
Date: Tue, 26 Oct 2021 19:06:59 +0700 [thread overview]
Message-ID: <YXfvY3n9wEwctjUR@danh.dev> (raw)
In-Reply-To: <20211026013452.1372122-4-eschwartz@archlinux.org>
On 2021-10-25 21:34:52-0400, Eli Schwartz <eschwartz@archlinux.org> wrote:
> The %(describe) placeholder by default, like `git describe`, uses a
> seven-character abbreviated commit object name. This may not be
> sufficient to fully describe all commits in a given repository,
> resulting in a placeholder replacement changing its length because the
> repository grew in size. This could cause the output of git-archive to
> change.
>
> Add the --abbrev option to `git describe` to the placeholder interface
> in order to provide tools to the user for fine-tuning project defaults
> and ensure reproducible archives.
>
> One alternative would be to just always specify --abbrev=40 but this may
> be a bit too biased...
>
> Signed-off-by: Eli Schwartz <eschwartz@archlinux.org>
> ---
>
> Notes:
> With regard to validating that an integer is passed, I attempt to parse the
> result using the same mechanism git-describe itself does in the abbrev
> callback, just with slightly different validation of what we have at the end...
> because of course here argval is the entire rest of the format string,
> including the ")".
>
> While testing that this actually does what it's supposed to do, I noticed that
> it doesn't validate junk like leading whitespace or plus signs... this is a
> problem for `git describe --abbrev=' +15'` too so I guess it's not my
> problem to fix...
>
> Documentation/pretty-formats.txt | 4 ++++
> pretty.c | 16 +++++++++++++++-
> t/t4205-log-pretty-formats.sh | 8 ++++++++
> 3 files changed, 27 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/pretty-formats.txt b/Documentation/pretty-formats.txt
> index 86ed801aad..57fd84f579 100644
> --- a/Documentation/pretty-formats.txt
> +++ b/Documentation/pretty-formats.txt
> @@ -222,6 +222,10 @@ The placeholders are:
> +
> ** 'tags[=<BOOL>]': Instead of only considering annotated tags,
> consider lightweight tags as well.
> +** 'abbrev=<N>': Instead of using the default number of hexadecimal digits
> + (which will vary according to the number of objects in the repository with a
> + default of 7) of the abbreviated object name, use <n> digits, or as many digits
> + as needed to form a unique object name.
> ** 'match=<pattern>': Only consider tags matching the given
> `glob(7)` pattern, excluding the "refs/tags/" prefix.
> ** 'exclude=<pattern>': Do not consider tags matching the given
> diff --git a/pretty.c b/pretty.c
> index 16b5366fed..44bfc49b38 100644
> --- a/pretty.c
> +++ b/pretty.c
> @@ -1218,9 +1218,10 @@ static size_t parse_describe_args(const char *start, struct strvec *args)
> {
> struct {
> char *name;
> - enum { OPT_BOOL, OPT_STRING, } type;
> + enum { OPT_BOOL, OPT_INTEGER, OPT_STRING, } type;
> } option[] = {
> { "tags", OPT_BOOL},
> + { "abbrev", OPT_INTEGER },
> { "exclude", OPT_STRING },
> { "match", OPT_STRING },
> };
> @@ -1245,6 +1246,19 @@ static size_t parse_describe_args(const char *start, struct strvec *args)
> found = 1;
> }
> break;
> + case OPT_INTEGER:
> + if (match_placeholder_arg_value(arg, option[i].name, &arg,
> + &argval, &arglen) && arglen) {
> + if (!arglen)
> + return 0;
> + char* endptr;
Other than the question pointed out by Eric,
with DEVELOPER=1, -Werror=declaration-after-statement
We'll need this change squashed in:
------- 8< -----
diff --git a/pretty.c b/pretty.c
index 289b5456c8..85d4ab008b 100644
--- a/pretty.c
+++ b/pretty.c
@@ -1249,9 +1249,9 @@ static size_t parse_describe_args(const char *start, struct strvec *args)
case OPT_INTEGER:
if (match_placeholder_arg_value(arg, option[i].name, &arg,
&argval, &arglen) && arglen) {
+ char* endptr;
if (!arglen)
return 0;
- char* endptr;
strtol(argval, &endptr, 10);
if (endptr - argval != arglen)
return 0;
------- >8 -----
> + strtol(argval, &endptr, 10);
> + if (endptr - argval != arglen)
> + return 0;
> + strvec_pushf(args, "--%s=%.*s", option[i].name, (int)arglen, argval);
> + found = 1;
> + }
> + break;
> case OPT_STRING:
> if (match_placeholder_arg_value(arg, option[i].name, &arg,
> &argval, &arglen) && arglen) {
> diff --git a/t/t4205-log-pretty-formats.sh b/t/t4205-log-pretty-formats.sh
> index d4acf8882f..35eef4c865 100755
> --- a/t/t4205-log-pretty-formats.sh
> +++ b/t/t4205-log-pretty-formats.sh
> @@ -1010,4 +1010,12 @@ test_expect_success '%(describe:tags) vs git describe --tags' '
> test_cmp expect actual
> '
>
> +test_expect_success '%(describe:abbrev=...) vs git describe --abbrev=...' '
> + test_when_finished "git tag -d tagname" &&
> + git tag -a -m tagged tagname &&
> + git describe --abbrev=15 >expect &&
> + git log -1 --format="%(describe:abbrev=15)" >actual &&
> + test_cmp expect actual
> +'
> +
> test_done
> --
> 2.33.1
>
--
Danh
next prev parent reply other threads:[~2021-10-26 12:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 1:42 [PATCH 0/3] Add some more options to the pretty-formats Eli Schwartz
2021-10-24 1:42 ` [PATCH 1/3] pretty.c: rename describe options variable to more descriptive name Eli Schwartz
2021-10-24 4:31 ` Junio C Hamano
2021-10-24 15:37 ` Eli Schwartz
2021-10-24 1:42 ` [PATCH 2/3] pretty: add tag option to %(describe) Eli Schwartz
2021-10-24 4:57 ` Junio C Hamano
2021-10-24 15:38 ` Eli Schwartz
2021-10-24 1:42 ` [PATCH 3/3] pretty: add abbrev " Eli Schwartz
2021-10-24 5:15 ` Junio C Hamano
2021-10-24 15:43 ` Eli Schwartz
2021-10-26 1:34 ` [PATCH v2 0/3] Add some more options to the pretty-formats Eli Schwartz
2021-10-26 1:34 ` [PATCH v2 1/3] pretty.c: rework describe options parsing for better extensibility Eli Schwartz
2021-10-26 5:18 ` Eric Sunshine
2021-10-26 20:05 ` Eli Schwartz
2021-10-26 1:34 ` [PATCH v2 2/3] pretty: add tag option to %(describe) Eli Schwartz
2021-10-26 5:25 ` Eric Sunshine
2021-10-26 20:06 ` Eli Schwartz
2021-10-26 1:34 ` [PATCH v2 3/3] pretty: add abbrev " Eli Schwartz
2021-10-26 5:36 ` Eric Sunshine
2021-10-26 12:06 ` Đoàn Trần Công Danh [this message]
2021-10-26 17:28 ` Eric Sunshine
2021-10-26 19:12 ` Eli Schwartz
2021-10-27 8:05 ` Carlo Arenas
2021-11-03 23:20 ` Johannes Schindelin
2021-11-04 9:29 ` Johannes Schindelin
2021-11-07 12:39 ` Eli Schwartz
2021-10-29 18:45 ` [PATCH v3 0/3] Add some more options to the pretty-formats Eli Schwartz
2021-10-29 18:45 ` [PATCH v3 1/3] pretty.c: rework describe options parsing for better extensibility Eli Schwartz
2021-10-29 20:11 ` Junio C Hamano
2021-10-29 21:06 ` Eli Schwartz
2021-10-29 21:34 ` Junio C Hamano
2021-10-29 18:45 ` [PATCH v3 2/3] pretty: add tag option to %(describe) Eli Schwartz
2021-10-29 20:18 ` Junio C Hamano
2021-10-29 21:14 ` Eli Schwartz
2021-10-29 21:46 ` Junio C Hamano
2021-10-29 21:28 ` Junio C Hamano
2021-10-29 21:44 ` Eli Schwartz
2021-10-29 18:45 ` [PATCH v3 3/3] pretty: add abbrev " Eli Schwartz
2021-10-29 18:51 ` Eric Sunshine
2021-10-29 19:04 ` Eli Schwartz
2021-10-31 17:15 ` [PATCH v4 0/3] Add some more options to the pretty-formats Eli Schwartz
2021-10-31 17:15 ` [PATCH v4 1/3] pretty.c: rework describe options parsing for better extensibility Eli Schwartz
2021-10-31 17:15 ` [PATCH v4 2/3] pretty: add tag option to %(describe) Eli Schwartz
2021-10-31 18:07 ` Junio C Hamano
2021-10-31 18:58 ` Eli Schwartz
2021-10-31 17:15 ` [PATCH v4 3/3] pretty: add abbrev " Eli Schwartz
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=YXfvY3n9wEwctjUR@danh.dev \
--to=congdanhqx@gmail.com \
--cc=eschwartz@archlinux.org \
--cc=git@vger.kernel.org \
/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).