git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Thomas Weißschuh" <thomas@t-8ch.de>, git@vger.kernel.org
Subject: Re: [PATCH] builtin: add git-default-branch command
Date: Wed, 03 Nov 2021 10:22:41 -0700	[thread overview]
Message-ID: <xmqqy2656tni.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2111021433010.56@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Tue, 2 Nov 2021 14:39:27 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> But we do have prior art in Git how to display similar information: `git
> var -l` will list e.g. `GIT_PAGER`, even if it is not configured
> explicitly.

Nice.  I was hoping that somebody would remember this one.

GIT_AUTHOR_IDENT and such that do not even exist as a variable is
part of "git var -l"; the name for the default initial branch falls
into the same category.

Thanks.

  parent reply	other threads:[~2021-11-03 17:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 14:01 [PATCH] builtin: add git-default-branch command Thomas Weißschuh
2021-10-30 17:18 ` Ævar Arnfjörð Bjarmason
2021-11-02 13:39 ` Johannes Schindelin
2021-11-02 16:44   ` [PATCH v2] var: add GIT_DEFAULT_BRANCH variable Thomas Weißschuh
2021-11-02 16:53     ` Ævar Arnfjörð Bjarmason
2021-11-02 17:35       ` Thomas Weißschuh
2021-11-02 19:14         ` Ævar Arnfjörð Bjarmason
2021-11-02 20:08           ` Thomas Weißschuh
2021-11-03 11:37       ` Jeff King
2021-11-03 16:48         ` Eric Sunshine
2021-11-03 18:21     ` Junio C Hamano
2021-11-03 18:53       ` [PATCH v3] " Thomas Weißschuh
2021-11-03 19:57         ` Eric Sunshine
2021-11-03 20:04           ` Junio C Hamano
2021-11-03 20:17           ` [PATCH v4] " Thomas Weißschuh
2021-11-03 20:23             ` Junio C Hamano
2021-11-03 17:22   ` Junio C Hamano [this message]
2021-11-03 23:44     ` [PATCH] builtin: add git-default-branch command Johannes Schindelin

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=xmqqy2656tni.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=thomas@t-8ch.de \
    /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 NNTP newsgroup(s).