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

Re: [PATCH v2 0/3] check for unpushed remotes in submodules

From
Jens Lehmann <jens.lehmann@web.de>
Date
Jul 28, 2011, 22:14 UTC
Message-ID
<4E31DF5A.4050307@web.de>
In-Reply-To
<7v39hqmb30.fsf@alter.siamese.dyndns.org>
Am 28.07.2011 21:58, schrieb Junio C Hamano:
Show 15 quoted lines
> Fredrik Gustafsson <iveqy@iveqy.com> writes:
> 
>> Regarding the discussion of superprojects with submodules that have no
>> remote tracking branches: A push will still be denied.
> 
> I have marked one part of the data synchronized across machines as
> "private" submodule (which contains my gpg keychains, encrypted password
> files, personaly memos, etc.) and push only the outer "shell" superproject
> (which has tools that I use everywhere to go to $HOME/bin among other
> things) to certain machines without the private parts, and the
> superproject is designed to work without a checkout (nor clone) of a
> submodule.
> 
> With this patch series, it sounds like I cannot use this repository
> structure anymore, which is sad.

Thanks for bringing this use case up. Now I understand why you asked if submodules without remote tracking branches should be checked too. We discussed that and couldn't think of a scenario where the user doesn't want to have remote tracking branches in a submodule, but we missed the use case you described here. Back to the drawing board ...

Previous: Junio C Hamano
Message 10 of 10 in “check for unpushed remotes in submodules”
  1. 0/3 check for unpushed remotes in submodulesFredrik Gustafsson, Jul 27, 2011
  2. 1/3 test whether push checks for unpushed remotes in submodulesFredrik Gustafsson, Jul 27, 2011
  3. 2/3 push: Don't push a repository with unpushed submodulesFredrik Gustafsson, Jul 27, 2011
  4. 3/3 push: Add the --no-recurse-submodules optionFredrik Gustafsson, Jul 27, 2011
  5. Junio C HamanoJul 28, 2011
  6. Jens LehmannJul 28, 2011
  7. Jens LehmannJul 29, 2011
  8. Junio C HamanoAug 1, 2011
  9. Junio C HamanoJul 28, 2011
  10. Jens LehmannJul 28, 2011

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.