git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: git@vger.kernel.org,  "Randall S. Becker" <rsbecker@nexbridge.com>
Subject: Re: What's cooking in git.git (Aug 2024, #03; Thu, 8)
Date: Fri, 09 Aug 2024 14:12:29 -0700	[thread overview]
Message-ID: <xmqqle15bdtu.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZk15_O=qasf1RspWfECFX1gQLTXZVMCeP3=RMC14K=2sg@mail.gmail.com> (Emily Shaffer's message of "Fri, 9 Aug 2024 12:49:47 -0700")

Emily Shaffer <nasamuffin@google.com> writes:

> On Thu, Aug 8, 2024 at 5:49 PM Junio C Hamano <gitster@pobox.com> wrote:
>> [Cooking]
>> [...]
>> * es/doc-platform-support-policy (2024-08-02) 1 commit
>>  - Documentation: add platform support policy
>>
>>  A policy document that describes platform support levels and
>>  expectation on platform stakeholders has been introduced.
>>
>>  Will merge to 'next'?
>>  source: <20240802221948.2367124-1-emilyshaffer@google.com>
>
> I haven't heard back much on v5, just a few "I will review this soon"
> and no update since then. Does that mean it's ready? Maybe other
> what's cooking readers missed this series and want to take a look? :)

FWIW, in my draft integration for the day (not yet pushed out) the
topic is already merged to 'next', so if somebody has spotted a
glaring error in it that cannot be fixed by additional patches on
top, they have only a few hours left to stop it.

Thanks.



      reply	other threads:[~2024-08-09 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  0:49 What's cooking in git.git (Aug 2024, #03; Thu, 8) Junio C Hamano
2024-08-09 12:40 ` Ghanshyam Thakkar
2024-08-09 19:49 ` Emily Shaffer
2024-08-09 21:12   ` 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=xmqqle15bdtu.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.com \
    --cc=rsbecker@nexbridge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).