On Wed, Sep 12, 2012 at 3:21 PM, Jens Lehmann <Jens.Lehmann@xxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html