Re: "submodule" mistake and a problem

From: Jens Lehmann <jens.lehmann@web.de>
Date: Oct 1, 2012, 16:40 UTC
Message-ID: <5069C760.2020603@web.de>
In-Reply-To: <CAHVO_93d92Ert35z1popk+X8HAAHX_jwTVdRCjrhNHrhTsvx2Q@mail.gmail.com>

Am 01.10.2012 14:05, schrieb Howard Miller:

Show 15 quoted lines

>>
>> Perhaps:
>>
>>   git rm -f --cached path/to/subdir   # remove from index, keep files
>>   git add path/to/subdir
>>
>> -- Hannes
> 
> Fantastic.... worked perfectly.  I'll write that down somewhere for
> the next time I do it :)
> 
> Is there a better way of handling sub-modules like that? I've looked
> at git submodules but just got into more of a mess. It would be nice
> to push a project complete with a (git) submodule upstream but it
> seems tricky or impossible.

Git submodules are distinct repositories by design, so you'd have to create an upstream repository for the submodule too to make that work. But I have the impression that you want to import another repository into a directory of your repo, so maybe git subtree is what you want.