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

Re: git push recurse.submodules behavior changed in 2.13

From
Stefan Beller <sbeller@google.com>
Date
Jun 12, 2017, 17:27 UTC
Message-ID
<CAGZ79ka=icZDS-6q2dGSxyeLxYw+Zd1M_DSWzmhmHYtbTQTvZw@mail.gmail.com>
In-Reply-To
<CAE5=+KUJr2=w3W=ZDTbd=L+8=KtwsV95Q7bcJassjzFncrnBKQ@mail.gmail.com>
On Sat, Jun 10, 2017 at 6:28 AM, John Shahid <jvshahid@gmail.com> wrote:
> bump. it's been a while and I'm still not clear what the next steps
> are. I'm happy to send a patch but I would like to get a consensus
> first.

What do you want a consensus on? (Is the change in 2.13 a bug or feature? I considered it enough of a feature to not pursue an urgent bug fix. Maybe I misunderstood the discussion)

This thread has diverged into lots of things that could be done. Jonathan pointed out 3 possible ways forward. (1) and (3) are being worked on, (2) is a new thing that nobody (not Brandon nor me) have on our radar for what to work on next. So maybe that is a good idea to get started when you want to get into sending a patch?

Also I have the impression that there may be one corner case, in which the handling of refspecs is missed, i.e. maybe we'd need a list (in the man page eventually) on what currently happens when recursing in combination with remote/refspecs or other options.

Previous: John ShahidNext: John Shahid
Message 9 of 10 in “git push recurse.submodules behavior changed in 2.13”
  1. John ShahidMay 27, 2017
  2. Junio C HamanoMay 29, 2017
  3. Stefan BellerMay 29, 2017
  4. John ShahidMay 30, 2017
  5. Brandon WilliamsMay 30, 2017
  6. Jonathan NiederMay 30, 2017
  7. John ShahidMay 31, 2017
  8. John ShahidJun 10, 2017
  9. Stefan BellerJun 12, 2017
  10. John ShahidJun 16, 2017

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.