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: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2025, #01; Sun, 3)
Date: Tue, 05 Aug 2025 03:24:22 -0700	[thread overview]
Message-ID: <xmqq4ium3w2x.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CDm5n0oZsXzvKz89jVg7E_h=1gqPFs2x7-UojdcY_Di_w@mail.gmail.com> (D. Ben Knoble's message of "Mon, 4 Aug 2025 21:22:07 -0400")

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

> .... This is true whether I use
> my copy of the topic or the one you publish (4c8db1e55c (builtin: also
> setup gently for --help-all, 2025-08-03)).

I think the breakage I saw was while testing the 'seen' branch as a
whole, so there may be some interactions with other topics.  IIRC,
it was running "git repo --help-all" when I saw the complaints.

  reply	other threads:[~2025-08-05 10:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04  8:23 What's cooking in git.git (Aug 2025, #01; Sun, 3) Junio C Hamano
2025-08-04  9:47 ` Patrick Steinhardt
2025-08-04 14:29   ` Junio C Hamano
2025-08-04 14:51     ` Patrick Steinhardt
2025-08-04 15:41       ` Jeff King
2025-08-05  0:34         ` Junio C Hamano
2025-08-05 12:51           ` Jeff King
2025-08-05 17:08             ` Junio C Hamano
2025-08-05 18:48               ` Jeff King
2025-08-05 13:05           ` Patrick Steinhardt
2025-08-05 13:44             ` Jeff King
2025-08-05 17:10             ` Junio C Hamano
2025-08-05  1:22 ` D. Ben Knoble
2025-08-05 10:24   ` Junio C Hamano [this message]
2025-08-05 16:23     ` D. Ben Knoble
2025-08-05 16:30       ` D. Ben Knoble
2025-08-05 19:06         ` Junio C Hamano
2025-08-05 19:18           ` Ben Knoble
2025-08-06 17:28           ` Lucas Seiki Oshiro
2025-08-06 18:34             ` Junio C Hamano

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=xmqq4ium3w2x.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    /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.