From: Jeff King <peff@peff.net>
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 15:37:05 -0400 [thread overview]
Message-ID: <20120912193705.GA26587@sigill.intra.peff.net> (raw)
In-Reply-To: <5050E0CA.7080907@web.de>
On Wed, Sep 12, 2012 at 09:21:46PM +0200, Jens Lehmann 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).
Yeah, in general I think the current system is fine. It might be
slightly more convenient to send out the update email, but finding the
right thread is more work for Junio (I guess you could just ignore that
and start a new thread, but for readers it is nice if it is connected to
the original series thread).
And I personally think it is nice to read through the whole list of
topics and their current status occasionally. I sometimes end up
commenting on a topic that I probably would not have otherwise seen that
way. Of course, I likely have a lot more git time than most people, so
the effort of skimming "what's cooking" is not too high for me.
-Peff
next prev parent reply other threads:[~2012-09-12 19:37 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 [this message]
2012-09-12 20:08 ` Dan Johnson
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=20120912193705.GA26587@sigill.intra.peff.net \
--to=peff@peff.net \
--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).