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

Re: [RFC v2] submodule: Respect requested branch on all clones

From
Francesco Pretto <ceztko@gmail.com>
Date
Jan 7, 2014, 21:51 UTC
Message-ID
<CALas-iiH0GCwy9WMWxBSGbUykwAKikaLUhfdDUbETv91QuM-7g@mail.gmail.com>
In-Reply-To
<20140107213739.GA29954@odin.tremily.us>
2014/1/7 W. Trevor King <wking@tremily.us>:
Show 8 quoted lines
>
> I'd be happy to hear ideas about superproject-branch-specific local
> overrides to a hypothetical submodule.<name>.local-branch, in the
> event that a developer doesn't like a default set in .gitmodules.  If
> I could think of a way to do that, we could avoid this heuristic
> approach, and make the local submodule.<name>.local-branch
> vs. remote-tracking submodule.<name>.branch distinction more obvious.
>

Uh, I think you got it wrong in the other thread: I didn't proposed such feature. I just wanted the attached submodule use case to be supported and of course "--branch means attached" is even easier to get this.

Previous: W. Trevor King
Message 2 of 2 in “Re: [RFC v2] submodule: Respect requested branch on all clones”
  1. W. Trevor KingJan 7, 2014
  2. Francesco PrettoJan 7, 2014

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.