git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH 1/1] push: introduce '--heads' option

From
ZheNing Hu <adlternative@gmail.com>
Date
Dec 5, 2022, 14:23 UTC
Message-ID
<CAOLTT8QcvPfXKap2aa6iyi0jq-cySL=XjDP2G2wG8m57=u0aGw@mail.gmail.com>
In-Reply-To
<20221205133525.60464-2-tenglong.tl@alibaba-inc.com>
Hi,
Teng Long <dyroneteng@gmail.com> 于2022年12月5日周一 21:44写道:
Show 14 quoted lines
>
> 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'.
>

"--all" sounds like it will include all things: branches, tags, but it only includes branches under ref/heads/, which does cause a little confusion for users.

Show 40 quoted lines
> To ensure compatibility, we cannot rename '--all' to another name
> directly, one way is, we can try to add a new option '--heads' which be
> identical with the functionality of '--all' to let the user understand
> the meaning of representation more clearly. Actually, We've more or less
> named options this way already, for example, in 'git-show-ref' and 'git
> ls-remote'.
>
> At the same time, we fix a related issue about the wrong help
> information of '--all' option in code.
>
> Signed-off-by: Teng Long <dyroneteng@gmail.com>
> ---
>  Documentation/git-push.txt |  1 +
>  builtin/push.c             | 13 +++++++------
>  t/t5523-push-upstream.sh   | 19 ++++++++++++-------
>  3 files changed, 20 insertions(+), 13 deletions(-)
>
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index 5bb1d5aae25..a5d18fb90b6 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -147,6 +147,7 @@ already exists on the remote side.
>  `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
>
>  --all::
> +--heads::
>         Push all branches (i.e. refs under `refs/heads/`); cannot be
>         used with other <refspec>.
>
> diff --git a/builtin/push.c b/builtin/push.c
> index 60ac8017e52..970cabaa78b 100644
> --- a/builtin/push.c
> +++ b/builtin/push.c
> @@ -588,11 +588,12 @@ int cmd_push(int argc, const char **argv, const char *prefix)
>         struct option options[] = {
>                 OPT__VERBOSITY(&verbosity),
>                 OPT_STRING( 0 , "repo", &repo, N_("repository"), N_("repository")),
> -               OPT_BIT( 0 , "all", &flags, N_("push all refs"), TRANSPORT_PUSH_ALL),
> +               OPT_BIT( 0 , "all", &flags, N_("push all branches"), TRANSPORT_PUSH_ALL),
> +               OPT_BIT( 0 , "heads", &flags, N_("push all branches"), TRANSPORT_PUSH_ALL),
Maybe OPT_ALIAS() will be better?
Previous: Teng LongNext: Teng Long
Message 3 of 18 in “push: introduce '--heads' option”
  1. 0/1 push: introduce '--heads' optionTeng Long, Dec 5, 2022
  2. 1/1 push: introduce '--heads' optionTeng Long, Dec 5, 2022
  3. ZheNing HuDec 5, 2022
  4. Teng LongDec 6, 2022
  5. Felipe ContrerasApr 28, 2023
  6. Teng LongApr 30, 2023
  7. 0/1 push: introduce '--branches' optionTeng Long, May 6, 2023
  8. 1/1 push: introduce '--branches' optionTeng Long, May 6, 2023
  9. 0/1 push: introduce '--branches' optionTeng Long, May 6, 2023
  10. Junio C HamanoDec 5, 2022
  11. Teng LongDec 15, 2022
  12. Teng LongApr 28, 2023
  13. Junio C HamanoApr 28, 2023
  14. Teng LongApr 30, 2023
  15. 0/1 push: introduce '--branches' optionTeng Long, May 6, 2023
  16. 1/1 push: introduce '--branches' optionTeng Long, May 6, 2023
  17. Junio C HamanoMay 6, 2023
  18. Teng LongMay 7, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.