On Wed, Nov 11, 2015 at 03:09:18PM +0100, Lars Schneider wrote:
> Apparently this does not clone the submodules with "--depth 1" (using Git
> 2.4.9). As a workaround I tried:
>
> git clone --depth 1 --single-branch
> cd
> git submodule update --init --recursive --depth 1
>
> However, this does
+cc Stanislav, who came up with the other thread for passing --remote
to git submodule
On Thu, Nov 12, 2015 at 1:39 AM, Lars Schneider
wrote:
>> Notice the other email thread, which suggests to include --remote into the
>> call to git submodule update depending on a branch config option being
>>
On 11 Nov 2015, at 21:09, Stefan Beller wrote:
> On Wed, Nov 11, 2015 at 11:19 AM, Stefan Beller wrote:
>> On Wed, Nov 11, 2015 at 6:09 AM, Lars Schneider
>> wrote:
>>> Hi,
>>>
>>> I have a clean build machine and I want to clone my source code to this
>>> machine while transferring only the
On Wed, Nov 11, 2015 at 11:19 AM, Stefan Beller wrote:
> On Wed, Nov 11, 2015 at 6:09 AM, Lars Schneider
> wrote:
>> Hi,
>>
>> I have a clean build machine and I want to clone my source code to this
>> machine while transferring only the minimal necessary amount of data.
>> Therefore I use this
On Wed, Nov 11, 2015 at 6:09 AM, Lars Schneider
wrote:
> Hi,
>
> I have a clean build machine and I want to clone my source code to this
> machine while transferring only the minimal necessary amount of data.
> Therefore I use this command:
>
> git clone --recursive --depth 1 --single-branch
T
Hi,
I have a clean build machine and I want to clone my source code to this machine
while transferring only the minimal necessary amount of data. Therefore I use
this command:
git clone --recursive --depth 1 --single-branch
Apparently this does not clone the submodules with "--depth 1" (using
6 matches
Mail list logo
