From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [GIT PULL] Documentation for 6.14
Date: Wed, 22 Jan 2025 06:57:59 -0700 [thread overview]
Message-ID: <87cygfdk7s.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAHk-=whEWhHYkj96zyxoBY81J_afP3tAq==F8+zjRix7hwgvQg@mail.gmail.com>
Linus Torvalds <torvalds@linuxfoundation.org> writes:
> On Mon, 20 Jan 2025 at 11:48, Jonathan Corbet <corbet@lwn.net> wrote:
>>
>> - Clarifying that Git commit IDs >12chars are OK
>
> Wel,, I'm not sure that was an improvement.
>
> I'd rather not see stupid extra random characters.
>
> We'll see. Hopefully people realize that "at least 12" means 12. Not
> some random other number.
I took it because it seemed that consistency in the documentation was
better than conflicting advice. If the policy is really "exactly 12
characters", though, we should probably make it read that way
instead...?
jon
next prev parent reply other threads:[~2025-01-22 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 19:48 [GIT PULL] Documentation for 6.14 Jonathan Corbet
2025-01-22 2:03 ` Linus Torvalds
2025-01-22 13:57 ` Jonathan Corbet [this message]
2025-01-22 16:02 ` Linus Torvalds
2025-01-22 2:06 ` pr-tracker-bot
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=87cygfdk7s.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.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