git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2010, #02 draft; Wed, 06)
Date: Wed, 06 Jan 2010 19:43:57 -0800	[thread overview]
Message-ID: <7vvdfeeg02.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100107122334.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Thu\, 07 Jan 2010 12\:23\:34 +0900")

Nanako Shiraishi <nanako3@lavabit.com> writes:

> 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".
>> ...
>> 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.

      reply	other threads:[~2010-01-07  3:44 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 ` What's cooking in git.git (Jan 2010, #02 draft; Wed, 06) Nanako Shiraishi
2010-01-07  3:43   ` Junio C Hamano [this message]

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=7vvdfeeg02.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nanako3@lavabit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).