From: Nanako Shiraishi <nanako3@lavabit.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2010, #02 draft; Wed, 06)
Date: Thu, 07 Jan 2010 12:23:34 +0900 [thread overview]
Message-ID: <20100107122334.6117@nanako3.lavabit.com> (raw)
In-Reply-To: <7vvdfenaar.fsf@alter.siamese.dyndns.org>
Quoting Junio C Hamano <gitster@pobox.com>
> 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.
For what it's worth, I think this new format very easy to spot the differences and much nicer.
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
next prev parent reply other threads:[~2010-01-07 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 22:22 What's cooking in git.git (Jan 2010, #02 draft; Wed, 06) Junio C Hamano
2010-01-06 22:25 ` Junio C Hamano
2010-01-07 4:42 ` Sverre Rabbelier
2010-01-08 7:42 ` What's cooking in git.git (Jan 2010, #02; Thu, 07) Junio C Hamano
2010-01-07 3:23 ` Nanako Shiraishi [this message]
2010-01-07 3:43 ` What's cooking in git.git (Jan 2010, #02 draft; Wed, 06) Junio C Hamano
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=20100107122334.6117@nanako3.lavabit.com \
--to=nanako3@lavabit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.