All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #04; Wed, 10)
Date: Wed, 10 Sep 2025 14:45:42 -0700	[thread overview]
Message-ID: <xmqqqzweoubd.fsf@gitster.g> (raw)
In-Reply-To: <ef86dd0f-f581-49d8-97e4-d20aed50d671@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 10 Sep 2025 23:12:24 +0200")

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

> On Wed, Sep 10, 2025, at 23:03, Junio C Hamano wrote:
>> * kh/you-still-use-whatchanged-fix (2025-09-09) 7 commits
>>  - BreakingChanges: remove claim about whatchanged reports
>>  - whatchanged: remove not-even-shorter clause
>>  - whatchanged: tell users the git-log(1) equivalent
>>  - you-still-use-that??: help the user help themselves
>>  - t0014: test shadowing of aliases for a sample of builtins
>>  - git: allow alias-shadowing deprecated builtins
>>  - git: add `deprecated` category to --list-cmds
>>
>>  Update "do you still use it?" message given by a command that is
>>  deeply deprecated and allow us to suggest alternatives.
>>
>>  Will merge to 'next'?
>>  source: <cover.1757446619.git.code@khaugsbakk.name>
>
> I need to follow up on the leak that Peff found.

Thanks, both.  Will hold.

      reply	other threads:[~2025-09-10 21:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 21:03 What's cooking in git.git (Sep 2025, #04; Wed, 10) Junio C Hamano
2025-09-10 21:12 ` Kristoffer Haugsbakk
2025-09-10 21:45   ` 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=xmqqqzweoubd.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.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.