From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Stefan Beller <sbeller@google.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jan 2016, #04; Wed, 20)
Date: Tue, 26 Jan 2016 10:47:57 +0100 [thread overview]
Message-ID: <C1F7518D-3898-4F53-8BAD-60B5648D4B5B@gmail.com> (raw)
In-Reply-To: <xmqqk2n33jxq.fsf@gitster.mtv.corp.google.com>
On 21 Jan 2016, at 00:33, 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 tip of 'master' now has second batch of topics merged, some of
> which should later be merged to 'maint'. There are a few topics
> that are v2.7.0 regression fixes still cooking outside 'master',
> which also need to be merged to 'maint' for the maintenance release.
>
> You can find the changes described here in the integration branches of the
> repositories listed at
>
> http://git-blame.blogspot.com/p/git-public-repositories.html
Hi Junio,
Did you miss the topic "submodule: extend die message on failed checkout with depth argument" or do you not agree with it ($gmane/282779)? Stefan Beller reviewed the commits ($gmane/283666 and $gmane/283851).
Thanks,
Lars
next prev parent reply other threads:[~2016-01-26 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 23:33 What's cooking in git.git (Jan 2016, #04; Wed, 20) Junio C Hamano
2016-01-21 12:09 ` jc/rerere-multi (was: What's cooking in git.git (Jan 2016, #04; Wed, 20)) Johannes Sixt
2016-01-21 22:07 ` jc/rerere-multi Junio C Hamano
2016-03-08 22:15 ` jc/rerere-multi Junio C Hamano
2016-01-22 16:58 ` What's cooking in git.git (Jan 2016, #04; Wed, 20) Johannes Schindelin
2016-01-22 17:57 ` Junio C Hamano
2016-01-26 9:47 ` Lars Schneider [this message]
2016-01-26 22:58 ` Junio C Hamano
2016-01-27 8:46 ` Lars Schneider
2016-01-27 18:03 ` Stefan Beller
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=C1F7518D-3898-4F53-8BAD-60B5648D4B5B@gmail.com \
--to=larsxschneider@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.
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).