From: Jeff King <peff@peff•net>
To: Luna Schwalbe <dev@luna•gl>
Cc: git@vger•kernel.org, Junio C Hamano <gitster@pobox•com>
Subject: Re: [PATCH] doc: document and test `@` prefix for raw timestamps
Date: Tue, 2 Jun 2026 02:17:52 -0400 [thread overview]
Message-ID: <20260602061752.GA695568@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqfr35zt6h.fsf@gitster.g>
On Tue, Jun 02, 2026 at 09:23:34AM +0900, Junio C Hamano wrote:
> > + It is safer to prepend the `<unix-timestamp>` with `@`
> > + (e.g., `@0 +0000`), which forces Git to interpret it as a raw
> > + timestamp. This is required for values less than 100,000,000
> > + (which have fewer than 9 digits) to avoid confusion with other
> > + date formats (like `YYYYMMDD`).
>
> Does this "additional paragraph" format correctly, instead of
> rendered as a literal block (typically typeset in typewriter font,
> monospace)? Don't you need to do something like what is done for
> "ISO 8601::" that appears later in the same file? I.e. lose the
> four-space indent and replace the blank line before it with a single
> '+' list continuation operator?
Yes, I think so. As a tip for contributors, running:
cd Documentation
./doc-diff HEAD^ HEAD
is often good for seeing a rough approximation of the rendered doc. It
shows here that the result is incorrectly indented versus the rest of
the section.
Sadly it is somewhat limited in terms of typography, since it is diffing
the roff-rendered manpages. So you wouldn't realize that it is rendered
in a typewriter font, as you would if you looked at the html output.
Spot-checking the html is also a good thing to do when writing doc
patches.
-Peff
next prev parent reply other threads:[~2026-06-02 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 21:39 [PATCH] doc: document and test `@` prefix for raw timestamps Luna Schwalbe
2026-06-02 0:23 ` Junio C Hamano
2026-06-02 6:17 ` Jeff King [this message]
2026-06-02 8:15 ` Luna Schwalbe
2026-06-02 9:10 ` 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=20260602061752.GA695568@coredump.intra.peff.net \
--to=peff@peff$(echo .)net \
--cc=dev@luna$(echo .)gl \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(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