From: Junio C Hamano <gitster@pobox•com>
To: Teng Long <dyroneteng@gmail•com>
Cc: git@vger•kernel.org, --cc=avarab@gmail•com,
tenglong.tl@alibaba-inc•com, me@ttaylorr•com
Subject: Re: [RFC PATCH 0/1] push: introduce '--heads' option
Date: Tue, 06 Dec 2022 08:35:21 +0900 [thread overview]
Message-ID: <xmqqilippgp2.fsf@gitster.g> (raw)
In-Reply-To: <20221205133525.60464-1-tenglong.tl@alibaba-inc.com> (Teng Long's message of "Mon, 5 Dec 2022 21:35:24 +0800")
Teng Long <dyroneteng@gmail•com> writes:
> From: Teng Long <dyroneteng@gmail•com>
>
> This RFC patch try to introduce a new option '--heads' in 'git-push' subcmd. The
> value of this patch may come from my personal point of view, and the patch might
> not have enough tests so far. It's pleasure to hear any suggestion, test
> scenario which need to be covered or any test method which need to be noticed if
> it's worthy.
My knee-jerk reaction is to avoid "--heads" and instead use
"--branches", if this is about pushing all local branches. The
option "--heads" may still remain in some commands added to the
system in the earliest part of our history, but soon we started
to use "branch" over "head", as it is a more commonly used word.
How should it interact with --follow-tags? Just as if you listed
all local branch names on the command line? I.e. is
git push $URL --heads
equivalent to the long-hand
git push $URL $(git for-each-ref --format='%(refname)' refs/heads/\*)
and because of that, does
git push $URL --any --other --option --heads
behave identically to the long-hand with these other options added?
next prev parent reply other threads:[~2022-12-05 23:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 13:35 [RFC PATCH 0/1] push: introduce '--heads' option Teng Long
2022-12-05 13:35 ` [RFC PATCH 1/1] " Teng Long
2022-12-05 14:23 ` ZheNing Hu
2022-12-06 12:18 ` Teng Long
2023-04-28 12:21 ` Felipe Contreras
2023-04-30 1:05 ` Teng Long
2023-05-06 11:27 ` [PATCH 0/1] push: introduce '--branches' option Teng Long
2023-05-06 11:27 ` [PATCH 1/1] " Teng Long
2023-05-06 11:36 ` [PATCH 0/1] " Teng Long
2022-12-05 23:35 ` Junio C Hamano [this message]
2022-12-15 12:27 ` [RFC PATCH 0/1] push: introduce '--heads' option Teng Long
2023-04-28 9:59 ` Teng Long
2023-04-28 18:48 ` Junio C Hamano
2023-04-30 1:09 ` Teng Long
2023-05-06 11:34 ` [PATCH 0/1] push: introduce '--branches' option Teng Long
2023-05-06 11:34 ` [PATCH 1/1] " Teng Long
2023-05-06 21:39 ` Junio C Hamano
2023-05-07 6:43 ` Teng Long
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=xmqqilippgp2.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=--cc=avarab@gmail$(echo .)com \
--cc=dyroneteng@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=me@ttaylorr$(echo .)com \
--cc=tenglong.tl@alibaba-inc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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