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

Derrick Stolee <stolee@gmail.com> writes:

> 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?

This was primarily designed to help guide me decide what topics to
merge to 'next' in what order, and it is pretty much a grep in the
main part of the report that duplicates what is already said down
there.  With the number of topics in the report, it may not be very
useful as a ToC, and while I do not mind adding one every time I
send out a new issue of the report, I do not know how it affects
readers to drown them by this list-of-topics at the top.

Another thing that is different in this and upcoming issue of the
report is that I tried to track down the "source" of each topic, so
that it becomes easy to go to a single web page I can view the
discussion on the topic by appending "source:" message ID after
https://lore.kernel.org/git/.  I am still not sure how sustainable
to keep doing this "source:" annotation (it is automated somewhat,
but needs manual sanity checks), so I won't promise keeping it in
the future, though.  At least, not yet.

Thanks.

  reply	other threads:[~2021-12-07 17:25 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
2021-12-07 17:25     ` Junio C Hamano [this message]
  -- 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq35n4ba4x.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=stolee@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).