From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: Incorrect URL for Release Notes on git-scm
Date: Wed, 19 Feb 2025 08:52:57 -0800 [thread overview]
Message-ID: <xmqq1pvtho5y.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD18tgq6f9N189tn2ZrV5cWU8u34EEpZhkwRosi8qUuhuw@mail.gmail.com> (Christian Couder's message of "Wed, 19 Feb 2025 09:28:48 +0100")
Christian Couder <christian.couder@gmail.com> writes:
> Thanks for the details. We are transitioning from ".txt" to ".adoc"
> for the extension of many of our documentation files and this is
> perhaps triggering this issue.
Yup, that seems to be exactly what happened. When we prepared the
transition, in https://lore.kernel.org/git/xmqqmsfl2gro.fsf@gitster.g/
I said:
Perhaps it may be enough keep the topic cooking a lot longer in
'next' than usual one calendar week. This of course requires that
those on the creator side echosystem are paying attention to 'next',
are capable of writing necessary adjustment (in my case, I would
tweak my tooling so that it uses "$filename.$suffix" instead of
hardcoded "txt" in the rest of the script, checks the presence of
Documention/git.adoc to tweak suffix from default "txt") for their
tooling, and can arrange to test their tooling with 'next'.
but apparently three weeks was not long enough for folks who are
maintaining the git-scm.com documentation machinery (or they were
not paying attention at all and even one year wouldn't have been
long enough X-<).
In any case, as I said earlier, Documentation/RelNotes/*.txt files
are never written as AsciiDoc (practically I am the only one who is
writing them) and are never processed and never meant to be
processed by the AsciiDoc/asciidoctor toolchain (I am not surprised
at all if stray punctuation letters I intended in a text document as
literal punctuation to be mistaken as AsciiDoc markups).
So from that point of view, it could be argued that we did not have
to rename them to .adoc suffix.
But I do not think it is a good direction to go in the longer term.
It may sweep this particular issue with a single link that the site
has into Documentation/RelNotes/ hierarchy under the rug, but it
forces everybody, including git-scm.com, to remember that everything
else in Documentation/ is ".adoc" but Documentation/RelNotes/ uses
".txt" as an exception when linking to our material. And because
there is no guarantee that we will never update our documentation
model so that the release notes are really done as proper AsciiDoc
marked-up text someday, such a move will force the downstream users
to transition to ".adoc" eventually.
Thanks.
prev parent reply other threads:[~2025-02-19 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 21:27 Incorrect URL for Release Notes on git-scm Bede Skinner-Vennell
2025-02-19 8:28 ` Christian Couder
2025-02-19 16:52 ` Junio C Hamano [this message]
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=xmqq1pvtho5y.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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).