From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2024, #05; Sat, 11)
Date: Mon, 13 May 2024 09:34:23 -0700 [thread overview]
Message-ID: <xmqqbk59hdrk.fsf@gitster.g> (raw)
In-Reply-To: <ZkGp9TqxO8Y5_kM_@tanuki> (Patrick Steinhardt's message of "Mon, 13 May 2024 07:49:41 +0200")
Patrick Steinhardt <ps@pks.im> writes:
>> * ps/pseudo-ref-terminology (2024-05-10) 10 commits
>> - refs: refuse to write pseudorefs
>> - ref-filter: properly distinuish pseudo and root refs
>> - refs: pseudorefs are no refs
>> - refs: classify HEAD as a root ref
>> - refs: root refs can be symbolic refs
>> - refs: refname `is_special_ref()` to `is_pseudo_ref()`
>> - refs: rename `is_pseudoref()` to `is_root_ref()`
>> - Documentation/glossary: define root refs as refs
>> - Documentation/glossary: clarify limitations of pseudorefs
>> - Documentation/glossary: redefine pseudorefs as special refs
>>
>> Terminology to call various ref-like things are getting
>> straightened out.
>>
>> Comments?
>> source: <cover.1715330206.git.ps@pks.im>
>
> There have been a bunch of comments on these topics already, and overall
> they have been positive. Is there something specific that you want to
> see here?
I did not get the feeling that we have given the series enough time
to be seen and get commented on; indeed v4 has not got enough time
to get any comments yet?
Also you haven't responded either positively or negatively to
comments on v3 07/10 by Peff?
next prev parent reply other threads:[~2024-05-13 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 23:29 What's cooking in git.git (May 2024, #05; Sat, 11) Junio C Hamano
2024-05-13 5:49 ` Patrick Steinhardt
2024-05-13 7:55 ` Patrick Steinhardt
2024-05-13 16:34 ` Junio C Hamano [this message]
2024-05-15 4:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbk59hdrk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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.
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).