All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,  Phillip Wood <phillip.wood123@gmail.com>,
	Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	 Harald Nordgren <haraldnordgren@gmail.com>,
	 Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH v2] status: compare against both upstream and push branch by default
Date: Sat, 24 Oct 2026 09:43:00 -0700	[thread overview]
Message-ID: <xmqq1p9f123v.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CBD2aGg_wDZZsT-mWJ99MXYUycx32JfsK8zJXfcmjTBDw@mail.gmail.com> (D. Ben Knoble's message of "Sat, 24 Oct 2026 09:49:26 -0400")

"D. Ben Knoble" <ben.knoble@gmail.com> writes:

>> control, so you may want to monitor its progress closely.  But isn't
>> your @{push} destination typically owned solely by you?  In other
>> words, aren't you the only one who pushes to it?  If so, whatever
>> you did locally would be the only change that could go on top of
>> @{push}, and unlike @{upstream} you would not see any unexpected
>> work over there appearing without your control.
>
> I think this paragraph assumes that either
>
> * I'm only pushing new commits to @{push}, or
> * I remember what the current state of @{push} is without checking.

I do strongly assume the former (I count revert in "new commits" in
this context, by the way), but not necessarily the latter.  But
unlike what appears in @{upstream}, I expect you would recognise
them when you see them.


  reply	other threads:[~2026-10-24 16:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 19:23 [PATCH] status: compare against both upstream and push branch by default Harald Nordgren via GitGitGadget
2026-10-19 22:54 ` Junio C Hamano
2026-10-20  9:16   ` Harald Nordgren
2026-10-20  9:33 ` Phillip Wood
2026-10-20 10:19   ` Harald Nordgren
2026-10-20 10:56     ` Kristoffer Haugsbakk
2026-10-20 13:22     ` Phillip Wood
2026-10-21 12:27 ` [PATCH v2] " Harald Nordgren via GitGitGadget
2026-10-23 17:43   ` Junio C Hamano
2026-10-23 18:48     ` Harald Nordgren
2026-10-23 22:10       ` Junio C Hamano
2026-10-23 22:54         ` Harald Nordgren
2026-10-23 23:07           ` Junio C Hamano
2026-10-24 13:49     ` D. Ben Knoble
2026-10-24 16:43       ` Junio C Hamano [this message]
2026-10-25 10:51 ` [PATCH v3] " Harald Nordgren via GitGitGadget

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=xmqq1p9f123v.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 \
    --cc=julia@jvns.ca \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=phillip.wood123@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.