Nanako Shiraishi <nanako3@xxxxxxxxxxx> writes: > Quoting Junio C Hamano <gitster@xxxxxxxxx> > >> I am experimenting with ideas to better manage the periodic "What's >> cooking" messages, and here is one of such attempt based on the current >> draft of the upcoming "2010 Jan, issue #02". >> ... >> Moved from [New Topics] to [Cooking] >> >> * da/difftool (2009-12-22) 2 commits >> - - git-difftool: Add '--gui' for selecting a GUI tool >> - - t7800-difftool: Set a bogus tool for use by tests >> + (merged to 'next' on 2010-01-06 at e957395) >> + + git-difftool: Add '--gui' for selecting a GUI tool >> + + t7800-difftool: Set a bogus tool for use by tests >> >> * jh/gitweb-cached (2010-01-03) 4 commits >> - gitweb: Makefile improvements >> - gitweb: Optionally add "git" links in project list page >> - gitweb: Add option to force version match >> - gitweb: Load checking >> + >> +Will merge to 'next', unless I hear objections within a few days. > > For what it's worth, I think this new format very easy to spot the > differences and much nicer. This is _not_ a "new format" per-se, but is primarily a demonstration of the external diff feature (all in 'todo' branch). While I think it is easier to view when I am interested in the differences since the previous issue (and that was why I wrote it) than the full list, its "incremental" nature cuts both ways. The primary reason I send out "What's cooking" is to make sure people are aware of topics that are _not_ going forward, to encourage them to be involved by helping such topics. When some topics are moved from Cooking to Stalled category, they will show up in the incremental report, but after that, until they start moving again, they won't be shown in the incremental report. That defeats the whole point of sending the "What's cooking" messages. Topics that are in motion are watched actively by testers, developers and documenters. They don't need as much exposure as stalled ones. -- 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