Junio C Hamano da6e86d371 MaintNotes: clarify the purpose of maint->master upmerge
Even though the paragraph before this one is pretty clear that
topics are first merged to 'master' and then to 'maint', it was
misleading to say 'maint' is merged to 'master' to propagate fixes
forward, as most of the time, such an upmerge is a noop because
topics merged to 'maint' are usually merged to 'master' already.

These up-merges are done primarily to make sure that the tip of
'master' has updated release notes from all the maintenance tracks,
so be explicit about that to avoid confusion.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-01-08 12:55:22 -08:00
2005-11-05 10:58:46 -08:00
2010-01-04 23:50:58 -08:00
2008-04-08 22:21:12 -07:00
AT
2008-04-08 22:21:12 -07:00
CB
2016-04-20 14:43:53 -07:00
2017-10-30 15:07:38 +09:00
2011-06-22 17:14:33 -07:00
2006-05-04 16:01:16 -07:00
2010-12-08 15:33:59 -08:00
RB
2007-12-14 22:43:05 -08:00
2010-01-04 23:50:58 -08:00
2017-12-06 12:23:17 -08:00
2013-03-13 13:00:59 -07:00
RP
2007-12-14 22:43:05 -08:00
SE
2013-02-25 07:20:26 -08:00
SR
2012-04-26 13:37:12 -07:00
2009-01-23 10:50:03 -08:00
2008-07-05 22:10:40 -07:00
WC
2008-12-02 22:55:44 -08:00
2018-01-05 15:14:26 -08:00
WI
2008-12-02 22:55:44 -08:00
2011-05-30 13:43:28 -07:00

The compare-cooking.perl script is meant to help viewing the differences
between periodical "What's cooking" messages, and can be used as an
external diff driver by:

    $ git config diff.whatscooking.command ./compare-cooking.perl

to produce this section in your .git/config

    [diff "whatscooking"]
	command = ./compare-cooking.perl

You can use e.g.

    $ git log -p --ext-diff whats-cooking.txt
    $ git show --ext-diff whats-cooking.txt

to review the history.
Description
No description provided
Readme 611 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%