From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Short-term plans for the post 2.9 cycle
Date: Mon, 20 Jun 2016 09:46:02 -0700 [thread overview]
Message-ID: <CAGZ79kaHRz2GZN4FmQBA1wz4FhBWDwVifWX_bN09TAHAxF-wQA@mail.gmail.com> (raw)
In-Reply-To: <xmqqh9covlkb.fsf@gitster.mtv.corp.google.com>
On Sun, Jun 19, 2016 at 3:52 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Here are the list of topics that are in the "private edition" I use
> for every day work, grouped by where they sit in the the near-term
> plan of merging them up to 'next' and then to 'master'.
>
> These will be merged to 'master' soonish.
>
Thanks for such an overview!
next prev parent reply other threads:[~2016-06-20 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 22:52 Short-term plans for the post 2.9 cycle Junio C Hamano
2016-06-20 16:46 ` Stefan Beller [this message]
2016-06-20 17:05 ` Junio C Hamano
2016-06-24 15:48 ` Jeff King
2016-06-24 16:54 ` Junio C Hamano
2016-06-24 17:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGZ79kaHRz2GZN4FmQBA1wz4FhBWDwVifWX_bN09TAHAxF-wQA@mail.gmail.com \
--to=sbeller@google.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.
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).