From: Junio C Hamano <gitster@pobox.com>
To: Artur Bieniek <abieniek@antmicro.com>
Cc: Phillip Wood <phillip.wood123@gmail.com>,
Artur Bieniek via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Artur Bieniek <ar2rekb@gmail.com>
Subject: Re: [PATCH] pull: add --hard mode
Date: Thu, 20 Aug 2026 18:09:18 -0700 [thread overview]
Message-ID: <xmqqa4qgth35.fsf@gitster.g> (raw)
In-Reply-To: <2b9cc581-7c8e-4cb3-9524-2b466209ac7e@antmicro.com> (Artur Bieniek's message of "Thu, 20 Aug 2026 18:43:08 +0200")
Artur Bieniek <abieniek@antmicro.com> writes:
> One case where --ff-only does not seem to cover that audience is when
> the upstream branch itself is rewritten.
It does, doesn't it?
It is not like you want to always blindly follow them. Rewound
upstream is w warning-worthy event that the user should be notified
rather loudly, I would expect.
prev parent reply other threads:[~2026-08-21 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 11:34 [PATCH] pull: add --hard mode Artur Bieniek via GitGitGadget
2026-08-18 14:48 ` Junio C Hamano
2026-08-20 9:58 ` Phillip Wood
2026-08-20 15:59 ` Junio C Hamano
2026-08-20 16:43 ` Artur Bieniek
2026-08-20 17:29 ` Kristoffer Haugsbakk
2026-08-21 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=xmqqa4qgth35.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=abieniek@antmicro.com \
--cc=ar2rekb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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.