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 (Oct 2013, #04; Fri, 18)
Date: Tue, 22 Oct 2013 08:20:15 -0700 [thread overview]
Message-ID: <xmqqli1luyc0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20131019063447.GA18977@sigill.intra.peff.net> (Jeff King's message of "Sat, 19 Oct 2013 02:34:48 -0400")
Jeff King <peff@peff.net> writes:
> On Fri, Oct 18, 2013 at 03:14:49PM -0700, Junio C Hamano wrote:
>
>> * jn/add-2.0-u-A-sans-pathspec (2013-04-26) 1 commit
>> * jc/push-2.0-default-to-simple (2013-06-18) 1 commit
>> * jc/add-2.0-ignore-removal (2013-04-22) 1 commit
>> ...
>> Will cook in 'next' until Git 2.0.
>
> I notice that these are not actually in 'next', despite the
> descriptions. Should they be, to give them wider exposure?
We have been running with their respective preparatory migration
steps in the released versions, so we are ready to do so. These
last steps of the multi-step transition should probably cook in
'next' for a cycle or two before the final 2.0 development cycle.
prev parent reply other threads:[~2013-10-22 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 22:14 What's cooking in git.git (Oct 2013, #04; Fri, 18) Junio C Hamano
2013-10-19 6:34 ` Jeff King
2013-10-19 7:35 ` Felipe Contreras
2013-10-22 15:20 ` 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=xmqqli1luyc0.fsf@gitster.dls.corp.google.com \
--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.
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.