git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Julien Jerphanion via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Julien Jerphanion <git@jjerphan.xyz>
Subject: Re: [PATCH] Add `-u` short option for `git pull`
Date: Tue, 26 Aug 2025 07:51:16 -0700	[thread overview]
Message-ID: <xmqqikiam90b.fsf@gitster.g> (raw)
In-Reply-To: <pull.2037.git.git.1756147789443.gitgitgadget@gmail.com> (Julien Jerphanion via GitGitGadget's message of "Mon, 25 Aug 2025 18:49:48 +0000")

"Julien Jerphanion via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> From: Julien Jerphanion <git@jjerphan.xyz>
>
> Add the short form `-u` as an alias for `--set-upstream`
> in `git pull`, similarly to `git push` which supports both forms.
>
> This allows users to use `git pull -u <remote> <branch>` as a
> shorter alternative to `git pull --set-upstream <remote> <branch>`.

The above explains what it does.  It does not justify why it is
needed.  Surely it may allow them to type less, but is it something
they would do very often, like every other day or even twice an
hour?  If not, should 'set-upstream' squat on a short-and-sweet 'u',
robbing it from future developers to use it for more useful purpose?


  parent reply	other threads:[~2025-08-26 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 18:49 [PATCH] Add `-u` short option for `git pull` Julien Jerphanion via GitGitGadget
2025-08-26 13:19 ` D. Ben Knoble
2025-08-26 14:51 ` Junio C Hamano [this message]
2025-09-17 16:21   ` Julien Jerphanion
2025-09-18  0:32     ` Junio C Hamano
2025-09-18  7:42       ` Julien Jerphanion

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=xmqqikiam90b.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@jjerphan.xyz \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.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.
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).