From: "Kyle J. McKay" <mackyle@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2015, #07; Fri, 20)
Date: Fri, 20 Mar 2015 17:47:00 -0700 [thread overview]
Message-ID: <06716CEA-8980-4156-A67F-84B89872DCDD@gmail.com> (raw)
In-Reply-To: <CAGZ79kapUtq0DbcD65v_aKmCXHz3hjSkEh1MJH1nWr2DhSa5hw@mail.gmail.com>
On Mar 20, 2015, at 16:29, Stefan Beller wrote:
> On Fri, Mar 20, 2015 at 4:24 PM, Kyle J. McKay <mackyle@gmail.com>
> wrote:
>
>> On Mar 20, 2015, at 15:02, Junio C Hamano wrote:
>>
>>> * bc/object-id (2015-03-13) 10 commits
>> [snip]
>>> Will cook in 'next'.
>>
>> Has this been merged to 'next'?
>
> Usually Junio writes the mail first and then does a git push <all
> the branches>
> just before being done for the day. At least that's my suspicion as an
> observer of
> the timing when git fetch returns new shiny stuff and when these
> emails are sent.
I would expect that if it said, "Will merge to 'next'."
However the "What's cooking in git.git (Mar 2015, #06; Tue, 17)" also
says "Will cook in 'next'" for this topic so I think that perhaps it's
fallen through the cracks somehow.
-Kyle
next prev parent reply other threads:[~2015-03-21 0:47 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 [this message]
2015-03-21 3:20 ` Junio C Hamano
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=06716CEA-8980-4156-A67F-84B89872DCDD@gmail.com \
--to=mackyle@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).