From: "D. Ben Knoble" <ben.knoble@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2025, #01; Sun, 3)
Date: Mon, 4 Aug 2025 21:22:07 -0400 [thread overview]
Message-ID: <CALnO6CDm5n0oZsXzvKz89jVg7E_h=1gqPFs2x7-UojdcY_Di_w@mail.gmail.com> (raw)
In-Reply-To: <xmqqms8fbilv.fsf@gitster.g>
On Mon, Aug 4, 2025 at 4:23 AM Junio C Hamano <gitster@pobox.com> wrote:
> * dk/help-all (2025-08-03) 4 commits
> - builtin: also setup gently for --help-all
> - parse-options: refactor flags for usage_with_options_internal
> - t1517: fixup for ua/t1517-short-help-tests
> - Merge branch 'ua/t1517-short-help-tests' into dk/help-all
> (this branch uses ua/t1517-short-help-tests.)
>
> "git cmd --help-all" outside repository.
>
> Breaks t1517.296 under SANITIZE=leak?
> source: <20250803012613.54086-1-ben.knoble+github@gmail.com>
I don't see the link in the linux-leaks job of a recent CI run [1].
When I build with
make SANITIZE=leak CC=gcc-14
(since clang on my system doesn't support -fsantize=leak for
x86_64-apple-darwin21.6.0) and then
(cd t && prove t1517*)
then I get
t1517-outside-repo.sh .. ok
All tests successful.
Files=1, Tests=392, 22 wallclock secs ( 0.10 usr 0.01 sys + 5.26
cusr 4.40 csys = 9.77 CPU)
Result: PASS
So I don't think this topic is the problem. This is true whether I use
my copy of the topic or the one you publish (4c8db1e55c (builtin: also
setup gently for --help-all, 2025-08-03)).
[1]: https://github.com/benknoble/git/actions/runs/16706744996/job/47285921358
next prev parent reply other threads:[~2025-08-05 1:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 8:23 What's cooking in git.git (Aug 2025, #01; Sun, 3) Junio C Hamano
2025-08-04 9:47 ` Patrick Steinhardt
2025-08-04 14:29 ` Junio C Hamano
2025-08-04 14:51 ` Patrick Steinhardt
2025-08-04 15:41 ` Jeff King
2025-08-05 0:34 ` Junio C Hamano
2025-08-05 12:51 ` Jeff King
2025-08-05 17:08 ` Junio C Hamano
2025-08-05 18:48 ` Jeff King
2025-08-05 13:05 ` Patrick Steinhardt
2025-08-05 13:44 ` Jeff King
2025-08-05 17:10 ` Junio C Hamano
2025-08-05 1:22 ` D. Ben Knoble [this message]
2025-08-05 10:24 ` Junio C Hamano
2025-08-05 16:23 ` D. Ben Knoble
2025-08-05 16:30 ` D. Ben Knoble
2025-08-05 19:06 ` Junio C Hamano
2025-08-05 19:18 ` Ben Knoble
2025-08-06 17:28 ` Lucas Seiki Oshiro
2025-08-06 18:34 ` Junio C Hamano
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='CALnO6CDm5n0oZsXzvKz89jVg7E_h=1gqPFs2x7-UojdcY_Di_w@mail.gmail.com' \
--to=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).