[dundee] I'm a git (hopefully not really... what do you call people that use git?)

[Nistur]

Thanks all. I wasn't intending to nest submodules recursively, just
one shared submodule which is actually going to be more of an API for
the other project, and it shouldn't be updated often.

Submodules not updating automagically is a pain in the neck. Ahh well,
I'm sure I can manage with that.

Thanks again
Nistur


On Mon, Nov 8, 2010 at 3:06 PM, Rick Moynihan <rick.moynihan at gmail.com> wrote:
> A submodule is exactly what you need, though I'd encourage you to be
> frugal in your use of them... especially when nesting them
> recursively, as you will end up spending a lot of time propogating
> commits through your chain.  They're best used for versioning other
> repos things that don't change too often....  at least with regards
> the top level project.
>
> Submodules are great, but they can be a pain to administer.  Also they
> wont automatically checkout, so after cloning the top-level repo
> you'll need to do a:
>
> git submodule update --init --recursive
>
> Also when locking your top level project to a new commit in the
> submodule, be careful to do:
>
> git add submodule-foo
>
> and not:
>
> git add submodule-foo/
>
> As the later will stage every file in the submodule to the top-level project!
>
> The pro git book is a good resource, as is git help submodule.
>
> R.
>
> On 8 November 2010 14:42, Nistur <nistur at googlemail.com> wrote:
>> Thanks.
>>
>> Looks like a submodule's probably what I want then... the idea is that
>> repoA will check in (oops, push) libraries and header files, I'm
>> wanting to say to a branch, but I'm not sure if that's the correct
>> thing... but then repoB will ...pull in the "branch" into a submodule
>> for the project to compile against. I don't want to have repoB having
>> to drag down the whole source from repoA, or, even worse, having to
>> compile it all.
>>
>> I think my main problem is I'm still unsure what all the crazy words
>> all mean in git ;) so searching for what I think I want is probably
>> turning up the wrong things :P
>>
>> Thanks again
>>
>> Nistur
>>
>> On Mon, Nov 8, 2010 at 2:30 PM, Kris Davidson <davidson.kris at gmail.com> wrote:
>>> Mercurial?
>>>
>>> Git's not really my thing, had a slight look at it when trying to
>>> decide between Git, Mercurial and Bazaar. Anyway the Pro Git book is
>>> pretty good. http://progit.org/book/ |
>>> http://progit.org/book/ch6-6.html
>>>
>>> _______________________________________________
>>> dundee GNU/Linux Users Group mailing list
>>> dundee at lists.lug.org.uk  http://dundeelug.org.uk
>>> https://mailman.lug.org.uk/mailman/listinfo/dundee
>>> Chat on IRC, #tlug on irc.lug.org.uk
>>>
>>
>> _______________________________________________
>> dundee GNU/Linux Users Group mailing list
>> dundee at lists.lug.org.uk  http://dundeelug.org.uk
>> https://mailman.lug.org.uk/mailman/listinfo/dundee
>> Chat on IRC, #tlug on irc.lug.org.uk
>>
>
>
>
> --
> Rick Moynihan
> http://twitter.com/RickMoynihan
> http://delicious.com/InkyHarmonics
> http://sourcesmouth.co.uk/
>
> _______________________________________________
> dundee GNU/Linux Users Group mailing list
> dundee at lists.lug.org.uk  http://dundeelug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/dundee
> Chat on IRC, #tlug on irc.lug.org.uk
>