From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Patrick Steinhardt" <ps@pks.im>
Cc: git@vger.kernel.org,
"Kristoffer Haugsbakk" <code@khaugsbakk.name>,
"Karthik Nayak" <karthik.188@gmail.com>
Subject: Re: [PATCH 1/2] doc: refs: put ref migration warning under the command
Date: Wed, 05 Aug 2026 11:13:15 +0200 [thread overview]
Message-ID: <ef423f09-11dd-452b-9459-1baf017cde6f@app.fastmail.com> (raw)
In-Reply-To: <anLvVAyckm7S9Vo0@pks.im>
On Wed, Aug 5, 2026, at 10:07, Patrick Steinhardt wrote:
> On Tue, Aug 04, 2026 at 09:09:25PM +0200, Kristoffer Haugsbakk wrote:
>[snip]
>> By the way, I think I looked at the AsciiDoc admonition reference[1] and
>> saw `CAUTION` and `WARNING`, but now I don’t recall why I chose Caution
>> over Warning.
>>
>> 🔗 1: https://docs.asciidoctor.org/asciidoc/latest/blocks/admonitions/
>
> Hm, interesting. According to the docs, WARNING is to instruct the user
> of any lingering danger, whereas CAUTION asks them to act carefully. And
> while the first bullet point is merely a limitation (we cannot migrate
> worktrees), the second bullet point is indeed a warning that concurrent
> writers may cause harm. So going by that I think that a WARNING would
> indeed be a better fit.
Thanks. I’ll use Warning in the next version.
next prev parent reply other threads:[~2026-08-05 9:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 9:07 [PATCH 0/2] doc: refs: put ref migration warning under the command kristofferhaugsbakk
2026-07-31 9:07 ` [PATCH 1/2] " kristofferhaugsbakk
2026-08-04 14:30 ` Patrick Steinhardt
2026-08-04 19:09 ` Kristoffer Haugsbakk
2026-08-05 8:07 ` Patrick Steinhardt
2026-08-05 9:13 ` Kristoffer Haugsbakk [this message]
2026-07-31 9:07 ` [PATCH 2/2] doc: refs: linkgit to git-maintenance(1) kristofferhaugsbakk
2026-08-04 14:30 ` Patrick Steinhardt
2026-07-31 16:39 ` [PATCH 0/2] doc: refs: put ref migration warning under the command Junio C Hamano
2026-08-04 14:30 ` Patrick Steinhardt
2026-08-05 19:02 ` [PATCH v2 " kristofferhaugsbakk
2026-08-05 19:02 ` [PATCH v2 1/2] " kristofferhaugsbakk
2026-08-05 19:02 ` [PATCH v2 2/2] doc: refs: linkgit to git-maintenance(1) kristofferhaugsbakk
2026-08-06 5:15 ` [PATCH v2 0/2] doc: refs: put ref migration warning under the command Patrick Steinhardt
2026-08-06 17:32 ` Junio C Hamano
2026-08-06 6:20 ` [PATCH v3 " kristofferhaugsbakk
2026-08-06 6:20 ` [PATCH v3 1/2] " kristofferhaugsbakk
2026-08-06 6:20 ` [PATCH v3 2/2] doc: refs: linkgit to git-maintenance(1) kristofferhaugsbakk
2026-08-06 11:01 ` [PATCH v3 0/2] doc: refs: put ref migration warning under the command Karthik Nayak
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=ef423f09-11dd-452b-9459-1baf017cde6f@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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