Re: What's cooking in git.git (Feb 2024, #02; Fri, 2)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 5, 2024, 23:20 UTC
Message-ID: <xmqqjznimrbe.fsf@gitster.g>
In-Reply-To: <087d3438-98a1-46fe-89d9-8e7e1662151b@gmail.com>

Phillip Wood <phillip.wood123@gmail.com> writes:

Show 11 quoted lines

> I'm concerned that the UI could use some improvement. If I understand
> correctly the proposal is to make
>
> 	git for-each-ref
>
> and
>
> 	git for-each-ref ""
>
> behave differently so that the latter prints the pseudorefs from the
> current worktree and the former does not.

I would actually think that is perfectly sensible. The optional arguments for-each-ref name "filtering patterns" and you can view the behaviour of the command as using "refs/" as the default filtering pattern when nothing is given. But it is easy to defeat the unfortunate and historical default filtering pattern, by saying "we do not limit to any hierarchy, anything goes" by giving "" as the prefix.