From: Taylor Blau <me@ttaylorr.com>
To: "Wolfgang Müller" <wolf@oriole.systems>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 1/2] builtin/shortlog: explicitly set hash algo when there is no repo
Date: Wed, 16 Oct 2024 15:22:04 -0400 [thread overview]
Message-ID: <ZxASXLz4lA+E9MuQ@nand.local> (raw)
In-Reply-To: <20241016182124.48148-2-wolf@oriole.systems>
On Wed, Oct 16, 2024 at 08:21:23PM +0200, Wolfgang Müller wrote:
> Whilst git-shortlog(1) does not explicitly need any repository
> information when run without reference to one, it still parses some of
> its arguments with parse_revision_opt() which assumes that the hash
> algorithm is set. However, in c8aed5e8da (repository: stop setting SHA1
> as the default object hash, 2024-05-07) we stopped setting up a default
> hash algorithm and instead require commands to set it up explicitly.
>
> This was done for most other commands like in ab274909d4 (builtin/diff:
> explicitly set hash algo when there is no repo, 2024-05-07) but was
> missed for builtin/shortlog, making git-shortlog(1) segfault outside of
> a repository when given arguments like --author that trigger a call to
> parse_revision_opt().
Good analysis.
> Fix this for now by explicitly setting the hash algorithm to SHA1. Also
> add a regression test for the segfault.
Makes sense.
> Signed-off-by: Wolfgang Müller <wolf@oriole.systems>
> Thanks-to: Eric Sunshine <sunshine@sunshineco.com>
In the future, please ensure that your Signed-off-by is the last trailer
in the section to indicate that you have certified everything above it
(which in that case would include your Thanks-to here).
> @@ -143,6 +143,10 @@ fuzz()
> test_grep "too many arguments" out
> '
>
> +test_expect_success 'shortlog --author from non-git directory does not segfault' '
> + echo | nongit git shortlog --author=author
> +'
> +
Instead of 'echo |', I wonder if it would be just as good to write this
test as:
nongit git shortlog --author=author </dev/null
Thanks,
Taylor
next prev parent reply other threads:[~2024-10-16 19:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 18:34 [RFC PATCH] builtin/shortlog: explicitly set hash algo when there is no repo Wolfgang Müller
2024-10-15 9:33 ` Wolfgang Müller
2024-10-15 9:47 ` Kristoffer Haugsbakk
2024-10-15 19:54 ` Taylor Blau
2024-10-15 23:28 ` Taylor Blau
2024-10-16 8:15 ` Wolfgang Müller
2024-10-16 18:28 ` Taylor Blau
2024-10-15 11:48 ` [RFC PATCH v2] " Wolfgang Müller
2024-10-15 17:20 ` Eric Sunshine
2024-10-15 17:51 ` Wolfgang Müller
2024-10-16 5:32 ` Patrick Steinhardt
2024-10-16 8:47 ` Wolfgang Müller
2024-10-16 8:57 ` Patrick Steinhardt
2024-10-16 9:07 ` Wolfgang Müller
2024-10-16 18:52 ` Taylor Blau
2024-10-16 19:01 ` Wolfgang Müller
2024-10-17 5:04 ` Patrick Steinhardt
2024-10-16 9:48 ` Wolfgang Müller
2024-10-16 19:01 ` Taylor Blau
2024-10-16 19:14 ` Wolfgang Müller
2024-10-16 18:21 ` [PATCH v3 0/2] " Wolfgang Müller
2024-10-16 18:21 ` [PATCH v3 1/2] " Wolfgang Müller
2024-10-16 19:22 ` Taylor Blau [this message]
2024-10-16 19:37 ` Wolfgang Müller
2024-10-17 11:58 ` Patrick Steinhardt
2024-10-17 12:09 ` Wolfgang Müller
2024-10-17 12:11 ` Patrick Steinhardt
2024-10-16 18:21 ` [PATCH v3 2/2] shortlog: Test reading a log from a SHA256 repo in a non-git directory Wolfgang Müller
2024-10-16 19:25 ` Taylor Blau
2024-10-16 19:35 ` Wolfgang Müller
2024-10-16 19:45 ` Taylor Blau
2024-10-16 19:32 ` [PATCH v3 0/2] builtin/shortlog: explicitly set hash algo when there is no repo Taylor Blau
2024-10-16 19:38 ` Wolfgang Müller
2024-10-17 9:35 ` [PATCH v4] " Wolfgang Müller
2024-10-17 20:10 ` Taylor Blau
2024-10-17 22:02 ` Wolfgang Müller
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=ZxASXLz4lA+E9MuQ@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=wolf@oriole.systems \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.