git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Suggestions for "What's cooking"

From
Dan Johnson <computerdruid@gmail.com>
Date
Sep 12, 2012, 20:08 UTC
Message-ID
<CAPBPrnu9adK0mPLyVfimAzBEo7ZH+6HhqtLBRFWAvEA9mEGFfg@mail.gmail.com>
In-Reply-To
<5050E0CA.7080907@web.de>
On Wed, Sep 12, 2012 at 3:21 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
Show 20 quoted lines
> 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
Previous: Jeff KingNext: Junio C Hamano
Message 6 of 22 in “What's cooking in git.git (Sep 2012, #03; Mon, 10)”
  1. Junio C HamanoSep 10, 2012
  2. Teach rm to remove submodules unless they contain a git directoryJens Lehmann, Sep 11, 2012
  3. Junio C HamanoSep 11, 2012
  4. Suggestions for "What's cooking"Jens Lehmann, Sep 12, 2012
  5. Jeff KingSep 12, 2012
  6. Dan JohnsonSep 12, 2012
  7. Junio C HamanoSep 12, 2012
  8. Philip OakleySep 12, 2012
  9. Andrew ArdillSep 13, 2012
  10. Junio C HamanoSep 13, 2012
  11. Andrew ArdillSep 14, 2012
  12. Junio C HamanoSep 14, 2012
  13. Andrew ArdillSep 14, 2012
  14. Junio C HamanoSep 14, 2012
  15. Philip OakleySep 14, 2012
  16. Michael HaggertySep 13, 2012
  17. Philip OakleySep 13, 2012
  18. Junio C HamanoSep 13, 2012
  19. Junio C HamanoSep 14, 2012
  20. Michael HaggertySep 14, 2012
  21. Philip OakleySep 14, 2012
  22. Jens LehmannSep 12, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.