From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Jason Yundt" <jason@jasonyundt.email>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>
Subject: Re: [PATCH v2] gitweb: switch to an XHTML5 DOCTYPE
Date: Thu, 02 Jun 2022 15:09:39 -0700 [thread overview]
Message-ID: <xmqqmteuiuos.fsf@gitster.g> (raw)
In-Reply-To: <YpkwD1op18MY/qBa@camp.crustytoothpaste.net> (brian m. carlson's message of "Thu, 2 Jun 2022 21:47:59 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
>> > Subject: Re: [PATCH v2] gitweb: switch to an XHTML5 DOCTYPE
>> ...
>> > 2. mentions HTML5 like Bagas suggested.
>>
>> So, is it XHTML5, or HTML5, we want to see on the title?
>
> It's XHTML 5. Technically, it's the XML syntax of HTML 5, so I don't
> think we care much about the nit here.
I too don't care either way very much.
I just noticed the discrepancy between the title and the body, but
the mention of HTML5 is after the three-dash lines so nobody gets
hurt anyway ;-)
> We _could_ make this check for beginning of file, the XML declaration,
> and then the specified lines (e.g., with head(1)), but I don't really
> think that's necessary. We should be fine here for now, and if we decide
> we need that in the future, we can add it. I'd be happy with this as it
> stands.
Yup, thanks for sanity checking.
Will queue.
prev parent reply other threads:[~2022-06-02 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 1:26 [PATCH] gitweb: switch to a modern DOCTYPE Jason Yundt
2022-06-02 0:41 ` brian m. carlson
2022-06-02 6:10 ` Junio C Hamano
2022-06-02 7:26 ` Bagas Sanjaya
2022-06-02 11:43 ` [PATCH v2] gitweb: switch to an XHTML5 DOCTYPE Jason Yundt
2022-06-02 18:50 ` Junio C Hamano
2022-06-02 19:51 ` Jason Yundt
2022-06-02 21:47 ` brian m. carlson
2022-06-02 22:09 ` 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=xmqqmteuiuos.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=jason@jasonyundt.email \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.