Re: [RFC] Submodules in GIT

From: Martin Waitz <tali@admingilde.org>
Date: Dec 1, 2006, 12:12 UTC
Message-ID: <20061201121234.GQ18810@admingilde.org>
In-Reply-To: <45701B8D.1030508@b-i-t.de>

hoi :)

On Fri, Dec 01, 2006 at 01:09:49PM +0100, sf wrote:

Show 13 quoted lines

> Martin Waitz wrote:
> ...
> >So you not only store your submodule HEAD commit in the supermodule when 
> >you
> >do commit to the supermodule, it also means that your submodule HEAD
> >will be updated when you update your supermodule.
> 
> Why the magic? The typical workflow in git is
> 
> 1. You work on a branch, i.e. edit and commit and so on.
> 2. At some point, you decide to share the work you did on that branch 
> (e-mail a patch, merge into another branch, push upstream or let it by 
> pulled by upstream)

3. Other people want to use your new work.

-- 
Martin Waitz

$ 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.