From: Junio C Hamano <gitster@pobox.com>
To: Andy Koppe <andy.koppe@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>,
Karthik Nayak <karthik.188@gmail.com>,
Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH v4 0/5] root refs vs pseudorefs
Date: Thu, 12 Nov 2026 14:55:30 -0800 [thread overview]
Message-ID: <xmqqzevdfyn1.fsf@gitster.g> (raw)
In-Reply-To: <cover.1794520948.git.andy.koppe@gmail.com> (Andy Koppe's message of "Thu, 12 Nov 2026 22:05:36 +0000")
Andy Koppe <andy.koppe@gmail.com> writes:
> Changes in v4:
> - Glossary: stop contrasting pseudorefs with root refs, mention
> remote-tracking branches in the "ref" entry, and state that the list
> of per-worktree ref prefixes will not be extended.
> - git-ls-remote(1): describe what is shown by default, including
> peeling, and describe --refs and the example in those terms.
> - gitdatamodel(7): mention the root ref naming rules, and drop
> "so-called".
> - Reword the description and error message of rev-list --merge.
What I saw in "git co ak/root-refs-vs-pseudorefs && git diff @{1}"
looked all sensible.
prev parent reply other threads:[~2026-11-12 22:55 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 21:28 [PATCH 0/5] root refs vs pseudorefs Andy Koppe
2026-10-22 21:28 ` [PATCH 1/5] doc: glossary: add root ref and clarify pseudorefs Andy Koppe
2026-10-22 22:07 ` Junio C Hamano
2026-10-23 7:41 ` Patrick Steinhardt
2026-11-01 23:18 ` Andy Koppe
2026-10-22 21:28 ` [PATCH 2/5] doc: glossary: update per-worktree refs Andy Koppe
2026-10-23 7:41 ` Patrick Steinhardt
2026-11-01 23:26 ` Andy Koppe
2026-10-22 21:28 ` [PATCH 3/5] doc: stop calling root refs pseudorefs Andy Koppe
2026-10-23 7:41 ` Patrick Steinhardt
2026-11-01 23:44 ` Andy Koppe
2026-10-22 21:28 ` [PATCH 4/5] refs: " Andy Koppe
2026-10-23 7:41 ` Patrick Steinhardt
2026-11-01 23:46 ` Andy Koppe
2026-10-22 21:28 ` [PATCH 5/5] t: " Andy Koppe
2026-10-22 22:18 ` [PATCH 0/5] root refs vs pseudorefs Junio C Hamano
2026-10-23 13:21 ` Julia Evans
2026-11-01 23:07 ` Andy Koppe
2026-11-01 23:03 ` [PATCH v2 " Andy Koppe
2026-11-02 18:19 ` Julia Evans
2026-11-02 19:47 ` Andy Koppe
2026-11-02 21:00 ` Julia Evans
2026-11-02 22:19 ` Andy Koppe
2026-11-03 14:36 ` Julia Evans
2026-11-06 22:02 ` Andy Koppe
2026-11-02 21:49 ` Junio C Hamano
2026-11-01 23:03 ` [PATCH v2 1/5] doc: glossary: add root ref and clarify pseudorefs Andy Koppe
2026-11-03 11:29 ` Patrick Steinhardt
2026-11-03 18:30 ` Junio C Hamano
2026-11-01 23:03 ` [PATCH v2 2/5] doc: glossary: update per-worktree refs Andy Koppe
2026-11-03 11:29 ` Patrick Steinhardt
2026-11-01 23:03 ` [PATCH v2 3/5] doc: stop calling root refs pseudorefs Andy Koppe
2026-11-03 11:30 ` Patrick Steinhardt
2026-11-01 23:03 ` [PATCH v2 4/5] refs: " Andy Koppe
2026-11-01 23:03 ` [PATCH v2 5/5] t: " Andy Koppe
2026-11-06 21:31 ` [PATCH v3 0/5] root refs vs pseudorefs Andy Koppe
2026-11-06 21:31 ` [PATCH v3 1/5] doc: glossary: add root ref and clarify pseudorefs Andy Koppe
2026-11-06 22:13 ` Junio C Hamano
2026-11-12 22:29 ` Andy Koppe
2026-11-06 21:31 ` [PATCH v3 2/5] doc: glossary: update per-worktree refs Andy Koppe
2026-11-06 22:16 ` Junio C Hamano
2026-11-06 21:31 ` [PATCH v3 3/5] doc: stop calling root refs pseudorefs Andy Koppe
2026-11-06 23:08 ` Junio C Hamano
2026-11-12 22:52 ` Andy Koppe
2026-11-06 21:31 ` [PATCH v3 4/5] refs: " Andy Koppe
2026-11-06 23:16 ` Junio C Hamano
2026-11-06 21:31 ` [PATCH v3 5/5] t: " Andy Koppe
2026-11-12 22:05 ` [PATCH v4 0/5] root refs vs pseudorefs Andy Koppe
2026-11-12 22:05 ` [PATCH v4 1/5] doc: glossary: add root ref and clarify pseudorefs Andy Koppe
2026-11-12 22:05 ` [PATCH v4 2/5] doc: glossary: update per-worktree refs Andy Koppe
2026-11-12 22:05 ` [PATCH v4 3/5] doc: stop calling root refs pseudorefs Andy Koppe
2026-11-12 22:05 ` [PATCH v4 4/5] refs: " Andy Koppe
2026-11-12 22:05 ` [PATCH v4 5/5] t: " Andy Koppe
2026-11-12 22:55 ` Junio C Hamano [this message]
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=xmqqzevdfyn1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=andy.koppe@gmail.com \
--cc=git@vger.kernel.org \
--cc=julia@jvns.ca \
--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