From: Guillermo Gonzalez <guillermog@tricuspide.com>
Date: Tue, 17 Aug 2010 12:35:40 GMT
Subject: Re: Commit ID of a branch
Message-ID: <AANLkTikdVh9-60UjJW3vOp7jPA8_D_L+GqQ-9B5tcVeB@mail.gmail.com>
In-Reply-To: <4C69CD2C.9000700@gmail.com>

Thank you!

On 17 August 2010 01:43, Chris Packham <judge.packham@gmail.com> wrote:
> On 16/08/10 14:19, Guillermo wrote:
>> Hello,
>>
>> I want to write a script what checks in all my projects which is the submodule
>> commit that is registered in every git repo.
>>
>> Lets say we have the following structure:
>>
>> project1
>> - submodule1
>> project2
>> - submodule1
>>
>> I want to find out what file within the .git dir of every project contains the
>> proper submodule Commit ID that should be checkout with git submodule update.
>>
>> Regards,
>> Guillermo
>
> If I understand your question correctly, what you want is
>
>  git ls-tree HEAD submodule1
>
> Which will give you the sha1 of the commit in the submodule your project
> should be pointing to. We use this in various scripts at work.
>
> It is also possible to get this information (and more) from a slightly
> friendlier submodule command if you want it for non-script usage.
>
>  git submodule status
>



-- 
Guillermo