From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)
Date: Mon, 17 Sep 2018 15:54:08 -0700 [thread overview]
Message-ID: <xmqq36u768hb.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqy3c3agkr.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Fri, 14 Sep 2018 14:56:36 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> The tip of 'next' hasn't been rewound yet, but the states of many
> topics that were marked to "Cook in 'next'" read "Will merge to
> 'master'" now. I'll probably start merging a handful of topics that
> have been in 'next' down to 'master' tonight (they appear at the
> bottom of "log --first-parent master..pu" output).
A bunch of topics have been merged to 'master' and also to 'next'
with today's update. The tip of 'next' hasn't been rewound. I am
hoping that we can thin down the difference between 'master' and
'next' by merging a bit more topic from 'next' to 'master' without
adding more topics to 'next' for a week or so, and then rebuild
'next' at the end of that period, and then start to accept more
topics to 'next'.
next prev parent reply other threads:[~2018-09-17 22:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 21:56 What's cooking in git.git (Sep 2018, #03; Fri, 14) Junio C Hamano
2018-09-15 20:17 ` Antonio Ospite
2018-09-17 15:11 ` Junio C Hamano
2018-09-16 6:39 ` Duy Nguyen
2018-09-16 15:09 ` Ævar Arnfjörð Bjarmason
2018-09-17 2:39 ` Jeff King
2018-09-17 17:51 ` Junio C Hamano
2018-09-17 18:22 ` Jeff King
2018-09-17 18:26 ` Jonathan Nieder
2018-09-16 12:01 ` brian m. carlson
2018-09-17 15:10 ` Junio C Hamano
2018-09-17 18:35 ` Derrick Stolee
2018-09-17 19:04 ` Junio C Hamano
2018-09-17 22:54 ` Junio C Hamano [this message]
2018-09-19 3:49 ` [PATCH] pack-objects: handle island check for "external" delta base Jeff King
2018-09-19 18:34 ` Martin Ågren
2018-09-19 18:43 ` Jeff King
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=xmqq36u768hb.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).