From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2019, #01; Mon, 2)
Date: Mon, 2 Dec 2019 07:59:18 -0800 [thread overview]
Message-ID: <CABPp-BE01sXeNT9QtK+svfpeiVRvjw-U+R91BtJfiKhJCkrfxA@mail.gmail.com> (raw)
In-Reply-To: <xmqqpnh6yfrl.fsf@gitster-ct.c.googlers.com>
On Mon, Dec 2, 2019 at 6:19 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> Here are the topics that have been cooking. Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'. The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.
>
> The second batch of topics are now in 'master'; this was a rather
> large update, so there might be some fallout. Many topics are still
> in 'next' to be merged to 'master' soonish, and many others are
> waiting to be in 'next'.
Did you forget to push these out? I see:
$ git ls-remote git://github.com/gitster/git | grep refs/heads/master
d9f6f3b6195a0ca35642561e530798ad1469bd41 refs/heads/master
$ git ls-remote git://git.kernel.org/pub/scm/git/git.git | grep
refs/heads/master
d9f6f3b6195a0ca35642561e530798ad1469bd41 refs/heads/master
(...and the same for a few other clone URLs)
$ git log -1 d9f6f3b6195a0ca35642561e530798ad1469bd41
commit d9f6f3b6195a0ca35642561e530798ad1469bd41 (origin/master,
origin/HEAD, gitster/master)
Author: Junio C Hamano <gitster@pobox.com>
Date: Sun Nov 10 18:00:59 2019 +0900
The first batch post 2.24 cycle
Signed-off-by: Junio C Hamano <gitster@pobox.com>
next prev parent reply other threads:[~2019-12-02 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 14:16 What's cooking in git.git (Dec 2019, #01; Mon, 2) Junio C Hamano
2019-12-02 15:59 ` Elijah Newren [this message]
2019-12-02 21:05 ` Denton Liu
2019-12-03 16:34 ` Junio C Hamano
2019-12-03 16:38 ` Junio C Hamano
2019-12-04 6:19 ` Denton Liu
2019-12-04 18:14 ` Junio C Hamano
2019-12-04 18:53 ` Derrick Stolee
2019-12-06 21:31 ` Junio C Hamano
2019-12-13 13:38 ` Ed Maste
2019-12-13 13:58 ` Ed Maste
2019-12-13 19:02 ` Junio C Hamano
2019-12-16 2:26 ` Heba Waly
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=CABPp-BE01sXeNT9QtK+svfpeiVRvjw-U+R91BtJfiKhJCkrfxA@mail.gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).