From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Lars Schneider <larsxschneider@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)
Date: Tue, 19 Sep 2017 11:32:25 +0900 [thread overview]
Message-ID: <xmqqbmm7s9ja.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1709181637420.219280@virtualbox> (Johannes Schindelin's message of "Mon, 18 Sep 2017 16:41:39 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> Do you have a concrete suggestion to make these individual entries more
>> helpful for people who may want go back to the original thread in doing
>> so? In-reply-to: or References: fields of the "What's cooking" report
>> would not help. I often have the message IDs that made/helped me make
>> these individual comments in the description; they alone would not react
>> to mouse clicks, though.
>
> Oh gawd, not even more stuff piled onto the mail format. Please stop.
> ...
> It probably tries to serve too many purposes at the same time, and thereby
> none.
Well, this was started as my attempt to give a public service that
shows a summary of what is happening in the entire integration tree,
as there was nothing like that before (and going to github.com and
looking at 'pu' branch would not give you an easy overview). As
many people contribute many topics to the project, complaining that
it talks about too many topics would not get you anywhere.
If you find "What's cooking" report not serving your needs, and if
no one finds it not serving his or her needs, then I can stop
sending these out, of course, but I am not getting the impression
that we are at that point, at least not yet.
next prev parent reply other threads:[~2017-09-19 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 19:56 What's cooking in git.git (Aug 2017, #05; Tue, 22) Junio C Hamano
2017-08-23 1:00 ` Brandon Williams
2017-08-23 21:38 ` Lars Schneider
2017-08-24 19:33 ` Junio C Hamano
2017-09-15 16:18 ` Johannes Schindelin
2017-09-15 18:33 ` Junio C Hamano
2017-09-15 20:15 ` Johannes Schindelin
2017-09-15 21:22 ` Junio C Hamano
2017-09-18 14:41 ` Johannes Schindelin
2017-09-19 2:32 ` Junio C Hamano [this message]
2017-09-19 15:43 ` Johannes Schindelin
2017-09-19 16:07 ` Jonathan Nieder
2017-09-29 11:55 ` Johannes Schindelin
2017-09-19 16:20 ` Jonathan Nieder
2017-09-19 17:08 ` Nicolas Morey-Chaisemartin
2017-09-29 12:15 ` Johannes Schindelin
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=xmqqbmm7s9ja.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=larsxschneider@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.
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.