From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Kyle Lippincott via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Kyle Lippincott <spectral@google.com>
Subject: Re: [PATCH 1/3] set errno=0 before strtoX calls
Date: Fri, 02 Aug 2024 08:01:11 -0700 [thread overview]
Message-ID: <xmqq34nngea0.fsf@gitster.g> (raw)
In-Reply-To: <ZqxqtIJi4-xBL9Sj@tanuki> (Patrick Steinhardt's message of "Fri, 2 Aug 2024 07:12:20 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> It would be great if we could extend those wrappers to cover all of the
> integer types, convert our code base to use them, and then extend our
> "banned.h" banner. I'm of course not asking you to do that in this patch
> series.
A good #leftoverbits material.
> Out of curiosity, why do you hit those errors in your test setup? Do you
> use a special libc that behaves differently than the most common ones?
;-)
next prev parent reply other threads:[~2024-08-02 15:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 4:10 [PATCH 0/3] Small fixes for issues detected during internal CI runs Kyle Lippincott via GitGitGadget
2024-08-02 4:10 ` [PATCH 1/3] set errno=0 before strtoX calls Kyle Lippincott via GitGitGadget
2024-08-02 5:12 ` Patrick Steinhardt
2024-08-02 6:15 ` Kyle Lippincott
2024-08-02 15:01 ` Junio C Hamano [this message]
2024-08-02 4:10 ` [PATCH 2/3] strbuf: set errno to 0 after strbuf_getcwd Kyle Lippincott via GitGitGadget
2024-08-02 15:10 ` Junio C Hamano
2024-08-02 17:56 ` Kyle Lippincott
2024-08-02 4:10 ` [PATCH 3/3] t6421: fix test to work when repo dir contains d0 Kyle Lippincott via GitGitGadget
2024-08-02 15:13 ` Junio C Hamano
2024-08-02 20:58 ` [PATCH v2 0/3] Small fixes for issues detected during internal CI runs Kyle Lippincott via GitGitGadget
2024-08-02 20:58 ` [PATCH v2 1/3] set errno=0 before strtoX calls Kyle Lippincott via GitGitGadget
2024-08-02 21:18 ` Junio C Hamano
2024-08-02 20:58 ` [PATCH v2 2/3] strbuf: set errno to 0 after strbuf_getcwd Kyle Lippincott via GitGitGadget
2024-08-02 21:32 ` Junio C Hamano
2024-08-02 21:54 ` Eric Sunshine
2024-08-05 15:51 ` Junio C Hamano
2024-08-06 6:26 ` Patrick Steinhardt
2024-08-06 7:04 ` Kyle Lippincott
2024-08-02 23:51 ` Kyle Lippincott
2024-08-05 17:12 ` Kyle Lippincott
2024-08-02 20:58 ` [PATCH v2 3/3] t6421: fix test to work when repo dir contains d0 Kyle Lippincott via GitGitGadget
2024-08-02 21:41 ` Junio C Hamano
2024-08-03 0:03 ` Kyle Lippincott
2024-08-03 0:27 ` Junio C Hamano
2024-08-05 17:10 ` [PATCH v3 0/2] Small fixes for issues detected during internal CI runs Kyle Lippincott via GitGitGadget
2024-08-05 17:10 ` [PATCH v3 1/2] set errno=0 before strtoX calls Kyle Lippincott via GitGitGadget
2024-08-05 17:10 ` [PATCH v3 2/2] t6421: fix test to work when repo dir contains d0 Kyle Lippincott via GitGitGadget
2024-08-05 18:37 ` [PATCH v3 0/2] Small fixes for issues detected during internal CI runs 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=xmqq34nngea0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=ps@pks.im \
--cc=spectral@google.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).