All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Lars Schneider <larsxschneider@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)
Date: Fri, 15 Sep 2017 22:15:08 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1.1709152214100.219280@virtualbox> (raw)
In-Reply-To: <xmqqo9qbx14b.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Sat, 16 Sep 2017, Junio C Hamano wrote:

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

If that is the case, you will have to be okay with others responding to
your "What's cooking" mails instead of the original threads. That's what
you are buying into by having these "What's cooking" mails that are in no
usable way connected to the original threads.

Ciao,
Dscho

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

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

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1.1709152214100.219280@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.