git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2024, #02; Fri, 2)
Date: Mon, 05 Feb 2024 15:20:21 -0800	[thread overview]
Message-ID: <xmqqjznimrbe.fsf@gitster.g> (raw)
In-Reply-To: <087d3438-98a1-46fe-89d9-8e7e1662151b@gmail.com> (Phillip Wood's message of "Mon, 5 Feb 2024 18:57:49 +0000")

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

> 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.



  reply	other threads:[~2024-02-05 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03  8:23 What's cooking in git.git (Feb 2024, #02; Fri, 2) Junio C Hamano
2024-02-05 18:57 ` Phillip Wood
2024-02-05 23:20   ` Junio C Hamano [this message]
2024-02-06 13:56     ` Phillip Wood
2024-02-05 22:39 ` Taylor Blau

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=xmqqjznimrbe.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood123@gmail.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. 
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).