All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  "D. Ben Knoble" <ben.knoble@gmail.com>,
	 Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: [PATCH v2 0/2] remote: resolve "simple" @{push} when pushing to another remote
Date: Sat, 31 Oct 2026 18:09:29 -0700	[thread overview]
Message-ID: <xmqq5wyh2w8m.fsf@gitster.g> (raw)
In-Reply-To: <pull.2466.v2.git.git.1793433841.gitgitgadget@gmail.com> (Harald Nordgren via GitGitGadget's message of "Sat, 31 Oct 2026 08:03:59 +0000")

"Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com> writes:

> With push.default=simple and remote.pushDefault pointing at a fork, git push
> pushes the branch to the fork, but @{push} fails with "cannot resolve
> 'simple' push to a single destination".
>
> So git status cannot compare the branch with where it was pushed. Make
> @{push} resolve to where git push goes.
>
> Changes in v2:
>
>  * Moved the "simple" @{push} code out of branch_get_push_1() into its own
>    function in a new preparatory commit.

Looking good.  Will queue.

Thanks.

      parent reply	other threads:[~2026-11-01  1:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 12:43 [PATCH] remote: resolve "simple" @{push} when pushing to another remote Harald Nordgren via GitGitGadget
2026-10-28 22:24 ` D. Ben Knoble
2026-10-29 10:34   ` Harald Nordgren
2026-10-29 17:48   ` Junio C Hamano
2026-10-29 22:15     ` Harald Nordgren
2026-10-31  8:03 ` [PATCH v2 0/2] " Harald Nordgren via GitGitGadget
2026-10-31  8:04   ` [PATCH v2 1/2] remote: move "simple" @{push} resolution into a helper Harald Nordgren via GitGitGadget
2026-10-31  8:04   ` [PATCH v2 2/2] remote: resolve "simple" @{push} when pushing to another remote Harald Nordgren via GitGitGadget
2026-11-01  1:09   ` Junio C Hamano [this message]

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=xmqq5wyh2w8m.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=haraldnordgren@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.