Re: What's cooking in git.git (Jan 2010, #02 draft; Wed, 06)

> 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".
>
> This is an incremental update (the full version will follow shortly) that
> shows the changes since the previous issue, and was generated with a
> custom diff driver.  One of the things to notice is that the ones that
> only moved across sections (e.g. bg/maint-remote-update-default) without
> any other changes are shown without the list of commits.
>
> ----------------------------------------------------------------
>
> -What's cooking in git.git (Jan 2010, #01; Mon, 04)
> +What's cooking in git.git (Jan 2010, #02 draft; Wed, 06)
>
> --------------------------------------------------
> Born topics
>
> [New Topics]
>
>  * jc/maint-1.6.1-checkout-m-custom-merge (2010-01-06) 1 commit
>   - checkout -m path: fix recreating conflicts
>
>  * jn/makefile (2010-01-06) 4 commits
>   - Makefile: consolidate .FORCE-* targets
>   - Makefile: learn to generate listings for targets requiring special flags
>   - Makefile: use target-specific variable to pass flags to cc
>   - Makefile: regenerate assembler listings when asked
>
> --------------------------------------------------
> 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.