git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] push: add recurseSubmodules config option

From
Mike Crowe <mac@mcrowe.com>
Date
Nov 16, 2015, 18:31 UTC
Message-ID
<20151116183106.GA31731@mcrowe.com>
In-Reply-To
<CAGZ79kacpWFFWiE-KjwEQZC+3PZw2MrpsgQWLJyS82X5LF+Lqw@mail.gmail.com>
On Monday 16 November 2015 at 10:15:24 -0800, Stefan Beller wrote:
Show 23 quoted lines
> 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.
Thanks.
Mike.
Previous: Stefan BellerNext: Jens Lehmann
Message 3 of 7 in “push: add recurseSubmodules config option”
  1. push: add recurseSubmodules config optionMike Crowe, Nov 16, 2015
  2. Stefan BellerNov 16, 2015
  3. Mike CroweNov 16, 2015
  4. Jens LehmannNov 16, 2015
  5. Eric SunshineNov 16, 2015
  6. Junio C HamanoNov 30, 2015
  7. Mike CroweNov 30, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.