From: Dan Johnson <computerdruid@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Suggestions for "What's cooking"
Date: Wed, 12 Sep 2012 16:08:40 -0400 [thread overview]
Message-ID: <CAPBPrnu9adK0mPLyVfimAzBEo7ZH+6HhqtLBRFWAvEA9mEGFfg@mail.gmail.com> (raw)
In-Reply-To: <5050E0CA.7080907@web.de>
On Wed, Sep 12, 2012 at 3:21 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> Am 11.09.2012 21:41, schrieb Junio C Hamano:
>> Thanks. I wish all others paid attention to "What's cooking" like
>> you did here.
>>
>> And if it is hard to do so for whatever reason, suggest a better way
>> for me to publish "What's cooking" or an equivalent (I am interested
>> in finding the least bureaucratic way to help people and keep the
>> balls rolling).
>
> I think "What's cooking" makes lots of sense in its current form
> as one gets a very good overview over current development tracks.
>
> Maybe in addition it would be nice to email the author(s) of a
> series when the state changes or new comments are added (and to
> only include the relevant part from "What's cooking" there). For
> me it's not a big problem as I just have to grep for "submodule"
> to get the bits I care about, but I suspect others might have to
> invest much more time to check the current state of their series
> and may appreciate being mailed directly when something happens.
> Opinions?
I was thinking about this earlier. I wondered if it might even be
worth it just to CC the authors of all topics whose status has changed
since the last what's cooking, to make sure that they see updates
pertinent to them. I know that I at least have filters which catch
emails which CC me and promote them to my inbox, so I would see them
more readily.
My normal mode of operation is that when I have a patch in I check all
the "What's cooking" messages as if I was F5-ing a webpage, to follow
its status. Were I CCd on the message, I would be updated whenever the
mail was sent, which I would appreciate. This also has the nice side
effect of updating patch authors who are not subscribed to the list.
On the other hand, its possible some people would find that this
generated lots of noise, and it might also cause unrelated replies to
the "What's Cooking" message to CC all authors.
--
-Dan
next prev parent reply other threads:[~2012-09-12 20:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 23:55 What's cooking in git.git (Sep 2012, #03; Mon, 10) Junio C Hamano
2012-09-11 18:34 ` [PATCH v3] Teach rm to remove submodules unless they contain a git directory Jens Lehmann
2012-09-11 19:41 ` Junio C Hamano
2012-09-12 19:21 ` Suggestions for "What's cooking" Jens Lehmann
2012-09-12 19:37 ` Jeff King
2012-09-12 20:08 ` Dan Johnson [this message]
2012-09-12 21:49 ` Junio C Hamano
2012-09-12 22:49 ` Philip Oakley
2012-09-13 5:14 ` Andrew Ardill
2012-09-13 18:06 ` Junio C Hamano
2012-09-14 2:11 ` Andrew Ardill
2012-09-14 2:29 ` Junio C Hamano
2012-09-14 3:58 ` Andrew Ardill
2012-09-14 4:24 ` Junio C Hamano
2012-09-14 6:00 ` Philip Oakley
2012-09-13 7:09 ` Michael Haggerty
2012-09-13 7:21 ` Philip Oakley
2012-09-13 15:09 ` Junio C Hamano
2012-09-14 4:47 ` Junio C Hamano
2012-09-14 7:26 ` Michael Haggerty
2012-09-14 20:20 ` Philip Oakley
2012-09-12 19:24 ` [PATCH v3] Teach rm to remove submodules unless they contain a git directory Jens Lehmann
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=CAPBPrnu9adK0mPLyVfimAzBEo7ZH+6HhqtLBRFWAvEA9mEGFfg@mail.gmail.com \
--to=computerdruid@gmail.com \
--cc=Jens.Lehmann@web.de \
--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 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 NNTP newsgroup(s).