From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Thomas Weißschuh" <thomas@t-8ch.de>,
"Git List" <git@vger.kernel.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jeff King" <peff@peff.net>
Subject: Re: [PATCH v3] var: add GIT_DEFAULT_BRANCH variable
Date: Wed, 03 Nov 2021 13:04:42 -0700 [thread overview]
Message-ID: <xmqq5yt96m5h.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cR0PL-XtfC8v4-u1Taq6yOLO=2HSHsNBnzvzLCyM-whZA@mail.gmail.com> (Eric Sunshine's message of "Wed, 3 Nov 2021 15:57:27 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> earlier in the thread (i.e. create a dummy repo and ask it for its
> default branch)? Something like this (untested):
>
> (
> sane_unset GIT_TEST_... &&
> git init defbranch &&
> git -C defbranch symbolic-ref --short HEAD >expect &&
> git var GIT_DEFAULT_BRANCH >actual &&
> test_cmp expect actual
> )
So, the idea is to "observe" what the init command actually does,
and see if that matches the behaviour of the var command?
Sounds like a good way to ensure correctness to me.
Thanks.
next prev parent reply other threads:[~2021-11-03 20:04 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 [this message]
2021-11-03 20:17 ` [PATCH v4] " Thomas Weißschuh
2021-11-03 20:23 ` Junio C Hamano
2021-11-03 17:22 ` [PATCH] builtin: add git-default-branch command Junio C Hamano
2021-11-03 23:44 ` 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=xmqq5yt96m5h.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.