From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Karthik Nayak" <karthik.188@gmail.com>, git@vger.kernel.org
Cc: "Kristoffer Haugsbakk" <code@khaugsbakk.name>,
"Phillip Wood" <phillip.wood@dunelm.org.uk>,
"Junio C Hamano" <gitster@pobox.com>,
"Bence Ferdinandy" <bence@ferdinandy.com>,
"Taylor Blau" <me@ttaylorr.com>,
"Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: [PATCH v2 2/6] Documentation/git-update-ref.txt: remove safety paragraphs
Date: Sun, 20 Oct 2024 18:24:08 +0200 [thread overview]
Message-ID: <cfa378cd-2724-4c7e-9a86-68f4859d2d65@app.fastmail.com> (raw)
In-Reply-To: <CAOLa=ZRAGmgfSHjAx6-1q9qV-aJ_Ciw=RZ6kpygqbSO+yAUEeg@mail.gmail.com>
On Sun, Oct 20, 2024, at 13:13, karthik nayak wrote:
> kristofferhaugsbakk@fastmail.com writes:
>> […]
>> Such a safety warning is also much less relevant now, considering that
>> everyone who isn’t intentionally poking at the internal implementation
>> is using porcelain commands to manage `HEAD`.
>>
>> […]
>
> In the new reftable backend, HEAD would simply exist as a placeholder.
> So either we do as you did and remove this entirely or double down to
> say that writing to HEAD directly is not supported. I don't have a
> preference here, so this looks good!
I see now that I misread you. I thought you were talking about the
commit message. But you’re talking about the doc text.
I don’t think that this text needs to say that writing to `HEAD` is not
supported. Now the doc has implied that writing to `HEAD` is an option
since 2005. But I think that implication has been irrelevant for a long
time. We’re far away from the time when people had to update `HEAD`
manually.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2024-10-20 16:24 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 20:51 ref: with git update-ref? Bence Ferdinandy
2024-10-11 20:56 ` Kristoffer Haugsbakk
2024-10-11 21:04 ` Bence Ferdinandy
2024-10-11 21:28 ` Junio C Hamano
2024-10-12 19:41 ` Bence Ferdinandy
2024-10-13 9:34 ` Phillip Wood
2024-10-13 10:07 ` Kristoffer Haugsbakk
2024-10-13 12:09 ` karthik nayak
2024-10-13 15:39 ` Kristoffer Haugsbakk
2024-10-13 20:40 ` Bence Ferdinandy
2024-10-14 15:06 ` Kristoffer Haugsbakk
2024-10-15 19:03 ` [PATCH 0/6] doc: update-ref: amend old material and discuss symrefs kristofferhaugsbakk
2024-10-15 19:03 ` [PATCH 1/6] doc: update-ref: drop “flag” kristofferhaugsbakk
2024-10-16 20:45 ` Taylor Blau
2024-10-16 22:08 ` Eric Sunshine
2024-10-16 22:09 ` Taylor Blau
2024-10-17 15:30 ` Kristoffer Haugsbakk
2024-10-17 16:31 ` Eric Sunshine
2024-10-17 18:50 ` Taylor Blau
2024-10-15 19:03 ` [PATCH 2/6] doc: update-ref: remove safety paragraphs kristofferhaugsbakk
2024-10-16 20:47 ` Taylor Blau
2024-10-15 19:03 ` [PATCH 3/6] doc: update-ref: demote symlink to last section kristofferhaugsbakk
2024-10-15 19:03 ` [PATCH 4/6] doc: update-ref: remove confusing paragraph kristofferhaugsbakk
2024-10-16 20:51 ` Taylor Blau
2024-10-16 20:55 ` Kristoffer Haugsbakk
2024-10-16 20:57 ` Taylor Blau
2024-10-15 19:03 ` [PATCH 5/6] doc: update-ref: discuss symbolic links kristofferhaugsbakk
2024-10-15 19:08 ` Kristoffer Haugsbakk
2024-10-16 20:52 ` Taylor Blau
2024-10-15 19:03 ` [PATCH 6/6] doc: mutually link update-ref and symbolic-ref kristofferhaugsbakk
2024-10-16 8:51 ` [PATCH 0/6] doc: update-ref: amend old material and discuss symrefs Bence Ferdinandy
2024-10-16 20:54 ` Taylor Blau
2024-10-16 21:00 ` Kristoffer Haugsbakk
2024-10-19 19:59 ` [PATCH v2 " kristofferhaugsbakk
2024-10-19 19:59 ` [PATCH v2 1/6] Documentation/git-update-ref.txt: drop “flag” kristofferhaugsbakk
2024-10-20 11:09 ` karthik nayak
2024-10-19 19:59 ` [PATCH v2 2/6] Documentation/git-update-ref.txt: remove safety paragraphs kristofferhaugsbakk
2024-10-20 11:13 ` karthik nayak
2024-10-20 12:30 ` Kristoffer Haugsbakk
2024-10-20 16:24 ` Kristoffer Haugsbakk [this message]
2024-10-19 19:59 ` [PATCH v2 3/6] Documentation/git-update-ref.txt: demote symlink to last section kristofferhaugsbakk
2024-10-19 19:59 ` [PATCH v2 4/6] Documentation/git-update-ref.txt: remove confusing paragraph kristofferhaugsbakk
2024-10-19 19:59 ` [PATCH v2 5/6] Documentation/git-update-ref.txt: discuss symbolic refs kristofferhaugsbakk
2024-10-19 19:59 ` [PATCH v2 6/6] Documentation: mutually link update-ref and symbolic-ref kristofferhaugsbakk
2024-10-20 11:16 ` [PATCH v2 0/6] doc: update-ref: amend old material and discuss symrefs karthik nayak
2024-10-21 20:47 ` [PATCH v3 " kristofferhaugsbakk
2024-10-21 20:47 ` [PATCH v3 1/6] Documentation/git-update-ref.txt: drop “flag” kristofferhaugsbakk
2024-10-21 20:47 ` [PATCH v3 2/6] Documentation/git-update-ref.txt: remove safety paragraphs kristofferhaugsbakk
2024-10-21 20:47 ` [PATCH v3 3/6] Documentation/git-update-ref.txt: demote symlink to last section kristofferhaugsbakk
2024-10-21 20:47 ` [PATCH v3 4/6] Documentation/git-update-ref.txt: remove confusing paragraph kristofferhaugsbakk
2024-10-21 20:47 ` [PATCH v3 5/6] Documentation/git-update-ref.txt: discuss symbolic refs kristofferhaugsbakk
2024-10-21 20:47 ` [PATCH v3 6/6] Documentation: mutually link update-ref and symbolic-ref kristofferhaugsbakk
2024-10-21 20:50 ` [PATCH v3 0/6] doc: update-ref: amend old material and discuss symrefs Taylor Blau
2024-10-12 6:25 ` ref: with git update-ref? Andreas Schwab
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=cfa378cd-2724-4c7e-9a86-68f4859d2d65@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=bence@ferdinandy.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=me@ttaylorr.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=sunshine@sunshineco.com \
/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).