From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Mike Hommey <mh@glandium.org>,
git@vger.kernel.org, git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.44.0
Date: Sun, 25 Feb 2024 09:16:49 -0800 [thread overview]
Message-ID: <xmqqbk84jwfy.fsf@gitster.g> (raw)
In-Reply-To: <ZdrnvKRl8oGPJxOD@framework> (Patrick Steinhardt's message of "Sun, 25 Feb 2024 08:09:48 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> That's ultimately the reason why I don't want HEAD to look like a proper
> ref. But doing the "refs/heads/.invalid" workaround shouldn't be too bad,
> I guess.
Isn't the reason why reftable backend initializes refs/heads to be a
regular file exactly because we want to reject an attempt to create
such a file on the filesystem, though?
next prev parent reply other threads:[~2024-02-25 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 17:17 [ANNOUNCE] Git v2.44.0 Junio C Hamano
2024-02-24 5:10 ` Mike Hommey
2024-02-24 6:36 ` Patrick Steinhardt
2024-02-24 19:55 ` Mike Hommey
2024-02-25 7:09 ` Patrick Steinhardt
2024-02-25 17:16 ` Junio C Hamano [this message]
2024-02-27 7:02 ` Patrick Steinhardt
2024-02-27 14:29 ` Patrick Steinhardt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbk84jwfy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).