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

Re: [RFC] submodule+shallow clone feature request

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 10, 2010, 22:57 UTC
Message-ID
<alpine.DEB.1.00.1002102354010.20986@pacific.mpi-cbg.de>
In-Reply-To
<7vsk983fi4.fsf@alter.siamese.dyndns.org>
Hi,
On Wed, 10 Feb 2010, Junio C Hamano wrote:
Show 16 quoted lines
> Schuyler Duveen <sky@columbia.edu> writes:
> 
> > My use case is deploying from a git repository, which would be even more
> > graceful with the following features:
> >
> > 1. When 'git clone' has both --recursive and --depth, then submodules
> > are also checked out shallow (for speed/bandwidth).
> >
> > 2. Some way to specify an override on .gitmodules sources.  This is
> > because our .gitmodules includes public, read-only sources (github),
> > rather than our local repos we would prefer to deploy from (for the
> > purpose of reliability).
> 
> These should be doable if you do not use --recursive, so I don't think 
> they are insurmountable issues.  I suspect many people would welcome 
> such enhancements to the "git submodule" potty.

Yes. Note, though, that the problems of enhancing git-submodule are not technical, as we can learn from the recent history, including the lack of support for rebasing submodules (there _were_ patches!).

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 8 in “[RFC] submodule+shallow clone feature request”
  1. Schuyler DuveenFeb 10, 2010
  2. Avery PennarunFeb 10, 2010
  3. Junio C HamanoFeb 10, 2010
  4. Johannes SchindelinFeb 10, 2010
  5. Junio C HamanoFeb 10, 2010
  6. Johannes SchindelinFeb 10, 2010
  7. Re* [RFC] submodule+shallow clone feature requestJunio C Hamano, Feb 11, 2010
  8. Peter HuttererFeb 11, 2010

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.