All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)
Date: Tue, 7 Dec 2021 11:21:26 -0500	[thread overview]
Message-ID: <ef487c98-820c-010e-e3c9-39d60633b30f@gmail.com> (raw)
In-Reply-To: <xmqqilw1b4ry.fsf@gitster.g>

On 12/6/2021 8:08 PM, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
> 
>> FYI, here is how the topics listed in the report are categorized
>> (output from the 'cook -w' script I mentioned in the main report).
> 
> The output from the same command to summarize the current draft of
> the next issue of the "What's cooking" report looks like this.  As
> promised, unless a problem is found in it, a topic in 'next' will
> graduate almost automatically to 'master' after spending a week
> there, so by the end of this week we'll have ~40 topics graduating
> to 'master'.

Wow!!!

> Please pay extra attention to the list of topics slated for 'next'
> (with and without the '?') to stop topics that are not quite ready
> to go in to 'next' by mistake.
> 
> Thanks.

I found this output to be a particularly interesting way to get an
overview of everything going on. It almost looks appropriate for
being a "table of contents" for the main report. Have you thought
about adding it near the top of that report?

Thanks,
-Stolee


  reply	other threads:[~2021-12-07 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04  1:37 What's cooking in git.git (Dec 2021, #01; Fri, 3) Junio C Hamano
2021-12-07  1:08 ` Junio C Hamano
2021-12-07 16:21   ` Derrick Stolee [this message]
2021-12-07 17:25     ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2021-12-04  1:37 Junio C Hamano
2021-12-06 19:13 ` Phillip Wood
2021-12-06 19:24   ` Junio C Hamano
2021-12-08 12:42   ` Johannes Schindelin
2021-12-09  1:02     ` Junio C Hamano
2021-12-09 10:39     ` Phillip Wood
2021-12-07 15:54 ` Derrick Stolee

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=ef487c98-820c-010e-e3c9-39d60633b30f@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.