From: Jacob Keller <jacob.keller@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2016, #08; Wed, 24)
Date: Tue, 30 Aug 2016 23:25:18 -0700 [thread overview]
Message-ID: <CA+P7+xpjyhdNEMJuP6HB60Sj1uomsNRnZ9tAdcCKAwuRCbgOLQ@mail.gmail.com> (raw)
In-Reply-To: <CAGZ79kYVgCy95Pf14my_pq1qW=MB-3gF=FPf+S-VqO8k-8yf5A@mail.gmail.com>
On Tue, Aug 30, 2016 at 10:10 PM, Stefan Beller <sbeller@google.com> wrote:
>>
>> * sb/submodule-clone-rr (2016-08-17) 8 commits
>> - clone: recursive and reference option triggers submodule alternates
>> - clone: implement optional references
>> - clone: clarify option_reference as required
>> - clone: factor out checking for an alternate path
>> - submodule--helper update-clone: allow multiple references
>> - submodule--helper module-clone: allow multiple references
>> - t7408: merge short tests, factor out testing method
>> - t7408: modernize style
>>
>> I spotted a last-minute bug in v5, which is not a very good sign
>> (it shows that nobody is reviewing). Any more comments?
>>
>>
>
> Jacob Keller reviewed that series as announced in
>
> https://public-inbox.org/git/CA+P7+xpE=GoFWfdzmT+k=Zku8+YjEH-aOMsFUtJJJwFHa1hKDQ@mail.gmail.com/#t
>
> and concluded it is fine as in
>
> https://public-inbox.org/git/CA+P7+xrokr0ZGidQFuvpN+-J_WDjkaUropcnPGVjZHafc12AnQ@mail.gmail.com/
>
> Thanks,
> Stefan
Yep.
Thanks,
Jake
prev parent reply other threads:[~2016-08-31 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 21:16 What's cooking in git.git (Aug 2016, #08; Wed, 24) Junio C Hamano
2016-08-24 21:34 ` Jeff King
2016-08-24 22:01 ` Junio C Hamano
2016-08-26 14:09 ` Johannes Schindelin
2016-08-26 16:04 ` Junio C Hamano
2016-08-31 5:10 ` Stefan Beller
2016-08-31 6:25 ` Jacob Keller [this message]
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=CA+P7+xpjyhdNEMJuP6HB60Sj1uomsNRnZ9tAdcCKAwuRCbgOLQ@mail.gmail.com \
--to=jacob.keller@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).