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

Re: git submodules.

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Apr 28, 2008, 21:01 UTC
Message-ID
<20080428210139.GH26880@genesis.frugalware.org>
In-Reply-To
<1209412220.29267.22.camel@omicron.ep.petrobras.com.br>
On Mon, Apr 28, 2008 at 04:50:20PM -0300, Victor Bogado da Silva Lins <victor@bogado.net> wrote:
> Is there any documentation about how those work?

Yes. There is a chapter in the user manual and there is the git-submodule manpage.

Show 6 quoted lines
> What I need is this, I have a already existing git repository, that have
> a subdir that could be seen as submodule (by this I mean that he is
> related, but could have a different commit tree). The git repository
> already exists and has many commits that apply to either the submodule
> or the main module (I would say that there is no commit that touch
> both). So is it possible to separate them easily?
Yes, see git-filter-branch.
> Would it keep my older commits?

Not really, git-filter-branch will rewrite history, so the commit hashes will change. Of course no code will be lost, but after such a migration, people will not be able to easily just pull.

Previous: Victor Bogado da Silva Lins
Message 2 of 2 in “git submodules.”
  1. Victor Bogado da Silva LinsApr 28, 2008
  2. Miklos VajnaApr 28, 2008

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.