From: Ben Knoble <ben.knoble@gmail•com>
To: 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 <velocifyer@velocifyer•com>
Cc: git@vger•kernel.org, Jeff King <peff@peff•net>
Subject: Re: 0-Based indexes for git log
Date: Wed, 24 Sep 2025 11:26:13 -0400 [thread overview]
Message-ID: <B4B7BB74-9B69-4CDB-B4F2-FFB976A5B0CA@gmail.com> (raw)
In-Reply-To: <27456c8a-25f4-40f2-a791-efd35457d121@velocifyer.com>
> Le 24 sept. 2025 à 09:46, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 <velocifyer@velocifyer•com> a écrit :
>
>
>>
>> Are these date formats locale-specific? In both the US English and France French locales I use commonly, the 19th of September in 2025 _is_ a Friday. Showing 18 would only be confusing.
>
> Showing 19 confuses me because i'm used to 0-based indexes where the 19th is labeld as 18. Showing 18 would not cunfuse most people.
I would need evidence of that. Everyone I interact with agrees to write « 19 » when « 19th » is implied.
As I asked: is this particular to an community? I’m genuinely curious if there are groups or cultures that communicate this way.
As Peff points out, you can probably make commands display your own personal preference (or a locale should handle this for your community). But I don’t think this is something we can force on other people, because it would be confusing.
next prev parent reply other threads:[~2025-09-24 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 21:15 0-Based indexes for git log 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24 2:12 ` Ben Knoble
2025-09-24 13:46 ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24 15:26 ` Ben Knoble [this message]
2025-09-24 5:22 ` Jeff King
2025-09-24 13:42 ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24 15:43 ` Nico Williams
2025-09-24 16:53 ` Junio C Hamano
2025-09-24 17:11 ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24 17:28 ` Ben Knoble
2025-09-25 5:46 ` Patrick Steinhardt
2025-09-25 13:25 ` Junio C Hamano
2025-09-24 17:01 ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24 17:04 ` Nico Williams
2025-09-24 17:15 ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24 17:22 ` Emily Shaffer
2025-09-24 17:18 ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
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=B4B7BB74-9B69-4CDB-B4F2-FFB976A5B0CA@gmail.com \
--to=ben.knoble@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
--cc=velocifyer@velocifyer$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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