threads / discuss / 14663

git newbie - cloning / check out help

Subject: git newbie - cloning / check out help

## tl;dr

3 messages between Jul 24, 2008 and Jul 24, 2008.

replies: 2people: 2as markdown or json

Donald Brady· Jul 24, 2008, 21:24 UTC · lore

I am just ramping up on git and have the following scenario / issue:

  I have a git repository on server A.

  I clone it onto my machine B.

  In my local copy/repository on machine B I clone a repository on some 
third party server C.

  I commit my changes into B and push them to A.

  Now if I clone my repository from Server A onto my local machine
 in a different location I see all the source as normal but only the top
 level directory of C. Any source under that is not present.

What is the magic git incantation to make sure that I check out not only the code from my repository but any repositories that are cloned into it (recursive clone?)

Thanks

Donald

Petr Baudis· Jul 24, 2008, 23:15 UTC · re: Donald Brady · lore

Re: git newbie - cloning / check out help

Hi,

On Thu, Jul 24, 2008 at 09:24:34PM +0000, Donald Brady wrote:

Show 18 quoted lines

> I am just ramping up on git and have the following scenario / issue:
> 
>   I have a git repository on server A.
> 
>   I clone it onto my machine B.
> 
>   In my local copy/repository on machine B I clone a repository on some 
> third party server C.
> 
>   I commit my changes into B and push them to A.
> 
>   Now if I clone my repository from Server A onto my local machine
>  in a different location I see all the source as normal but only the top
>  level directory of C. Any source under that is not present. 
> 
> What is the magic git incantation to make sure that I check out 
> not only the code from my repository but  any repositories that
> are cloned into it (recursive clone?)

  we call this functionality "submodules" and the quickstart howto is:

	You have git repository on A

	You clone it onto your machine B

	git submodule add url directoryC

	You commit your changes into B and push them to A

	You do another clone of A and then within the clone

	git submodule update --init

For further details, see git-submodule(1).

-- 
				Petr "Pasky" Baudis
As in certain cults it is possible to kill a process if you know
its true name.  -- Ken Thompson and Dennis M. Ritchie

Donald Brady· Jul 24, 2008, 23:55 UTC · re: Petr Baudis · lore

Re: git newbie - cloning / check out help

Hi Peter.

I got it working now thanks to your pointer.

Donald

On Jul 24, 2008, at 4:15 PM, Petr Baudis wrote:

Show 44 quoted lines

>  Hi,
>
> On Thu, Jul 24, 2008 at 09:24:34PM +0000, Donald Brady wrote:
>> I am just ramping up on git and have the following scenario / issue:
>>
>>  I have a git repository on server A.
>>
>>  I clone it onto my machine B.
>>
>>  In my local copy/repository on machine B I clone a repository on  
>> some
>> third party server C.
>>
>>  I commit my changes into B and push them to A.
>>
>>  Now if I clone my repository from Server A onto my local machine
>> in a different location I see all the source as normal but only the  
>> top
>> level directory of C. Any source under that is not present.
>>
>> What is the magic git incantation to make sure that I check out
>> not only the code from my repository but  any repositories that
>> are cloned into it (recursive clone?)
>
>  we call this functionality "submodules" and the quickstart howto is:
>
> 	You have git repository on A
>
> 	You clone it onto your machine B
>
> 	git submodule add url directoryC
>
> 	You commit your changes into B and push them to A
>
> 	You do another clone of A and then within the clone
>
> 	git submodule update --init
>
> For further details, see git-submodule(1).
>
> -- 
> 				Petr "Pasky" Baudis
> As in certain cults it is possible to kill a process if you know
> its true name.  -- Ken Thompson and Dennis M. Ritchie