From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Derrick Stolee <stolee@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: What's cooking in git.git (May 2018, #01; Mon, 7)
Date: Tue, 08 May 2018 09:44:44 +0900 [thread overview]
Message-ID: <xmqqo9hrnfgj.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BFyj7SCfUbJzfjt==abORdUtfgRRywyjf0V73rDnygHGw@mail.gmail.com> (Elijah Newren's message of "Mon, 7 May 2018 09:33:56 -0700")
Elijah Newren <newren@gmail.com> writes:
> I'm actually curious what the "Will merge to 'master'" and "Will merge
> to 'next'" are intended to mean in general. I thought it meant that
> the topic would be merged the following week barring further
> discussion, but that hasn't always been the case ...
These have always been "eventually in some future", not "next
week".
A topic with potentially high impact tends to cook in 'next' longer
than a trivial typo fix, so that it has better chance of getting
stopped by the community dogfooding of 'next' before getting merged
to 'master' and bite the general public.
And the commit-graph thing certainly is a bigger beast I'd feel
safer if people tested heavily while it is in 'next' before it hits
'master'.
next prev parent reply other threads:[~2018-05-08 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 14:58 What's cooking in git.git (May 2018, #01; Mon, 7) Junio C Hamano
2018-05-07 15:20 ` Derrick Stolee
2018-05-07 16:33 ` Elijah Newren
2018-05-08 0:44 ` Junio C Hamano [this message]
2018-05-07 15:57 ` Elijah Newren
2018-05-08 1:01 ` Junio C Hamano
2018-05-08 17:05 ` Ben Peart
2018-05-10 4:25 ` 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=xmqqo9hrnfgj.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=newren@gmail.com \
--cc=stolee@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 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).