Re: [PATCH v2 1/2] push: check pushed ref for --force-if-includes

From: Tyler Cipriani <tyler@tylercipriani.com>
Date: Sep 10, 2026, 22:08 UTC
Message-ID: <CAHLx=Ok_0RntxYo5GsEQTmvxWy7B7S8KDHq=G+G5jWorPz3-3Q@mail.gmail.com>
In-Reply-To: <xmqqld99dk20.fsf@gitster.g>

On Thu, Sep 10, 2026 at 12:43 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 11 quoted lines

>
> Tyler Cipriani <tyler@tylercipriani.com> writes:
>
> > Message-ID: <20260908222056.1150748-2-tyler@tylercipriani.com>
> > References: <20260904210122.431757-1-tyler@tylercipriani.com>
>
> This is incorrectly threaded.  It is not made as a reply to the
> cover letter of v2; it is a reply to the cover letter of the initial
> iteration, and breaks automation.
>
> The same problem exists for [v2 2/2] as well.

Sorry for that. I had --in-reply-to on format-patch vs. send-email. I'll send a v3 with correct shallow threading.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.