From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2012, #02; Fri, 4)
Date: Thu, 10 May 2012 07:50:53 -0700 [thread overview]
Message-ID: <7vd36cozsi.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120510131255.GA2950@sigill.intra.peff.net> (Jeff King's message of "Thu, 10 May 2012 09:12:55 -0400")
Jeff King <peff@peff.net> writes:
> On Fri, May 04, 2012 at 04:06:18PM -0700, Junio C Hamano wrote:
>
>> --------------------------------------------------
>> [Graduated to "master"]
>>
>> * jk/maint-push-progress (2012-05-01) 3 commits
>> (merged to 'next' on 2012-05-01 at 2286130)
>> + t5541: test more combinations of --progress
>> + teach send-pack about --[no-]progress
>> + send-pack: show progress when isatty(2)
>>
>> "git push" over smart-http lost progress output and this resurrects it.
>>
>> Will merge to 'master'.
>
> I noticed that this graduated to master, but not to maint. Any reason?
Nobody goes direct to 'maint' if it is complex enough to go through
next/pu cycle these days.
$ git log -p Documentation/RelNotes/1.7.11.txt
will show, for example, jk/maint-config-bogus-section was merged as part
of the eighth batch (May 2) to 'master', but merged to 'maint' only after
we had it in 'master' for a bit without hearing any breakage caused by it.
Just like all the other features listed below the "Fixes since v1.7.10"
fold, the 'push progress' went into 'master' very recently with a note to
merge it later to 'maint', and we haven't seen 'later' yet.
next prev parent reply other threads:[~2012-05-10 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 23:06 What's cooking in git.git (May 2012, #02; Fri, 4) Junio C Hamano
2012-05-10 13:12 ` Jeff King
2012-05-10 14:50 ` Junio C Hamano [this message]
2012-05-10 15:13 ` Jeff King
2012-05-10 16:47 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vd36cozsi.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).