From: Jens Lehmann <Jens.Lehmann@web.de>
To: Mike Crowe <mac@mcrowe.com>, Stefan Beller <sbeller@google.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Heiko Voigt <hvoigt@hvoigt.net>
Subject: Re: [PATCH] push: add recurseSubmodules config option
Date: Mon, 16 Nov 2015 20:05:42 +0100 [thread overview]
Message-ID: <564A2906.7010902@web.de> (raw)
In-Reply-To: <20151116183106.GA31731@mcrowe.com>
Am 16.11.2015 um 19:31 schrieb Mike Crowe:
> On Monday 16 November 2015 at 10:15:24 -0800, Stefan Beller wrote:
>> The code itself looks good to me, one nit in the tests though.
>>
>>> @@ -79,6 +87,119 @@ test_expect_success 'push succeeds after commit was pushed to remote' '
>>> )
>>> '
>>>
>>> +test_expect_success 'push succeeds if submodule commit not on remote but using on-demand on command line' '
>>> + (
>>> + cd work/gar/bage &&
>>> + >recurse-on-demand-on-command-line &&
>>> + git add recurse-on-demand-on-command-line &&
>>> + git commit -m "Recurse on-demand on command line junk"
>>> + ) &&
>>> + (
>>> + cd work &&
>>> + git add gar/bage &&
>>> + git commit -m "Recurse on-demand on command line for gar/bage" &&
>>> + git push --recurse-submodules=on-demand ../pub.git master &&
>>> + # Check that the supermodule commit got there
>>> + git fetch ../pub.git &&
>>> + git diff --quiet FETCH_HEAD master
>>
>> Missing && chain here.
>
> Oh, well spotted! I'll provide an updated version.
Looking good for me too!
Cool, another issue from my Wiki that's being worked on!
next prev parent reply other threads:[~2015-11-16 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 13:24 [PATCH] push: add recurseSubmodules config option Mike Crowe
2015-11-16 18:15 ` Stefan Beller
2015-11-16 18:31 ` Mike Crowe
2015-11-16 19:05 ` Jens Lehmann [this message]
2015-11-16 23:13 ` Eric Sunshine
2015-11-30 18:31 ` Junio C Hamano
2015-11-30 19:00 ` Mike Crowe
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=564A2906.7010902@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=mac@mcrowe.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.
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).