All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2023, #06; Wed, 29)
Date: Wed, 29 Mar 2023 17:19:15 -0700	[thread overview]
Message-ID: <xmqqr0t75bwc.fsf@gitster.g> (raw)
In-Reply-To: <20230329231826.GA2314218@coredump.intra.peff.net> (Jeff King's message of "Wed, 29 Mar 2023 19:18:26 -0400")

Jeff King <peff@peff.net> writes:

>> * jk/document-pack-redundant-deprecation (2023-03-28) 1 commit
>>   (merged to 'next' on 2023-03-29 at cb64256b97)
>>  + pack-redundant: document deprecation
>> 
>>  Document that we have marked "pack-redundant" as deprecated.
>> 
>>  Will merge to 'master'.
>>  source: <20230328190641.GF18558@coredump.intra.peff.net>
>
> The application of the patch missed out on --scissors, I think.
> (I also expected it on top of jk/really-deprecate-pack-redundant, and
> for them to graduate together, but I don't think that matters much
> either way).

Yuck, that was very sloppy of me.  Thanks for catching.

  reply	other threads:[~2023-03-30  0:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 22:45 What's cooking in git.git (Mar 2023, #06; Wed, 29) Junio C Hamano
2023-03-29 23:18 ` Jeff King
2023-03-30  0:19   ` Junio C Hamano [this message]
2023-03-30  4:02 ` Elijah Newren
2023-03-30  4:05   ` Junio C Hamano
2023-04-01 19:07 ` Elijah Newren
2023-04-03 15:49   ` Junio C Hamano
2023-04-03 17:36   ` Junio C Hamano
2023-04-01 19:58 ` ps/ahead-behind-truncation-fix (Was: Re: What's cooking in git.git (Mar 2023, #06; Wed, 29)) Elijah Newren
2023-04-03 18:12 ` ps/fetch-ref-update-reporting " Jonathan Tan

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=xmqqr0t75bwc.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.