From: Felipe Contreras <felipe.contreras@gmail.com>
To: Teng Long <dyroneteng@gmail.com>, git@vger.kernel.org
Cc: --cc=avarab@gmail.com, tenglong.tl@alibaba-inc.com,
me@ttaylorr.com, Teng Long <dyroneteng@gmail.com>
Subject: Re: [RFC PATCH 1/1] push: introduce '--heads' option
Date: Fri, 28 Apr 2023 06:21:19 -0600 [thread overview]
Message-ID: <644bba3f96e3b_1c66e29436@chronos.notmuch> (raw)
In-Reply-To: <20221205133525.60464-2-tenglong.tl@alibaba-inc.com>
Teng Long wrote:
> From: Teng Long <dyroneteng@gmail.com>
>
> The '--all' option of git-push built-in cmd support to push all branches
> (refs under refs/heads) to remote. Under the usage, a user can easlily
> work in some scenarios, for example, branches synchronization and batch
> upload.
>
> '--all' was introduced for a long time, meanwhile, git supports to
> customize the storage location under "refs/". when a new git user see
> the usage like, 'git push origin --all', we might feel like we're
> pushing _all_ the refs instead of just branches without looking at the
> documents until we found the related description of it or '--mirror'.
Completely agree.
This is something I spotted a long time ago. Although I would prefer
`--branches` over `--heads`.
--
Felipe Contreras
next prev parent reply other threads:[~2023-04-28 12:21 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 [this message]
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 ` [RFC PATCH 0/1] push: introduce '--heads' option Junio C Hamano
2022-12-15 12:27 ` 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
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=644bba3f96e3b_1c66e29436@chronos.notmuch \
--to=felipe.contreras@gmail.com \
--cc=--cc=avarab@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=tenglong.tl@alibaba-inc.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).