From: Junio C Hamano <gitster@pobox.com>
To: Julien Jerphanion <git@jjerphan.xyz>
Cc: "gitgitgadget@gmail.com" <gitgitgadget@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Add `-u` short option for `git pull`
Date: Wed, 17 Sep 2025 17:32:52 -0700 [thread overview]
Message-ID: <xmqqplboa9cb.fsf@gitster.g> (raw)
In-Reply-To: <VVHyXy0fQW1fnBgiAFswUMEMMX4wnc3YIZWSRtSJzZbHOt0dfY0wCJt69MDxfue54cN2gPd8StlVtW2ERYKZcEs8Hpm7X5TaXrygCN2rK-A=@jjerphan.xyz> (Julien Jerphanion's message of "Wed, 17 Sep 2025 16:21:12 +0000")
Julien Jerphanion <git@jjerphan.xyz> writes:
[jc: line-wrapped an overly long single line]
> Having this shortcut would be really useful for some use cases
> where one needs to pull locally branches from forks before
> updating them and pushing them again on the fork instead than on
> the upstream project (typical use case for conda-forge's
> feedstocks).
Sorry, do you mean that you stay on a single branch, and then you
would pull from one place with "git pull -u" followed by "git push"
to push back there, and repeat that for other places, practically
redefining the meaning of the "upstream" to "the last remote
repository I pulled from and I am supposed to push to that remote
and nowhere else in my workflow"?
next prev parent reply other threads:[~2025-09-18 0:32 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
2025-09-17 16:21 ` Julien Jerphanion
2025-09-18 0:32 ` Junio C Hamano [this message]
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=xmqqplboa9cb.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).