git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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: Sat, 16 Sep 2017 03:33:56 +0900	[thread overview]
Message-ID: <xmqqo9qbx14b.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1709151816390.219280@virtualbox> (Johannes Schindelin's message of "Fri, 15 Sep 2017 18:18:19 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> If you want *contributors* to ping the thread themselves, how about
> *posting your updates there, too*?

I do not understand this comment at all.  That is what I and others
already and always do by responding to the patches, and when trying
to see if a topic is still alive, with thread-specific responses and
pings.

If you are demanding that "What's cooking" report to be sent as a
response to all the topics, that will *NOT* going to happen.  It is
meant to give a summary of the current state to help contributors
and reviewers be aware of what is happening across the entire tree
and not limited to a specific topic.

  reply	other threads:[~2017-09-15 18:34 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 [this message]
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
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

  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=xmqqo9qbx14b.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. 
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).