From: Junio C Hamano <gitster@pobox.com>
To: "Kyle J. McKay" <mackyle@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2015, #07; Fri, 20)
Date: Fri, 20 Mar 2015 20:20:58 -0700 [thread overview]
Message-ID: <xmqqegojc9yd.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <423416FC-1048-4D3A-B997-F1F796627242@gmail.com> (Kyle J. McKay's message of "Fri, 20 Mar 2015 16:24:16 -0700")
"Kyle J. McKay" <mackyle@gmail.com> writes:
>> Will cook in 'next'.
>
> Has this been merged to 'next'? Even fetching
> github.com/gitster/git.git I'm only seeing it in pu:
That was a short-hand for "will merge and cook in 'next'" ;-)
I had an impression that the series may see at least one reroll to
polish it further before it gets ready for 'next', as I only saw
discussions on the tangent (e.g. possible futures) and didn't see
serious reviews of the code that we will actually be using.
next prev parent reply other threads:[~2015-03-21 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 22:02 What's cooking in git.git (Mar 2015, #07; Fri, 20) Junio C Hamano
2015-03-20 23:24 ` Kyle J. McKay
2015-03-20 23:29 ` Stefan Beller
2015-03-21 0:47 ` Kyle J. McKay
2015-03-21 3:20 ` Junio C Hamano [this message]
2015-03-21 20:15 ` brian m. carlson
2015-03-22 19:08 ` 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=xmqqegojc9yd.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mackyle@gmail.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.