Git development
 help / color / mirror / Atom feed
* git newbie - cloning / check out help
@ 2008-07-24 21:24 Donald Brady
  2008-07-24 23:15 ` Petr Baudis
  0 siblings, 1 reply; 3+ messages in thread
From: Donald Brady @ 2008-07-24 21:24 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: git newbie - cloning / check out help
  2008-07-24 21:24 git newbie - cloning / check out help Donald Brady
@ 2008-07-24 23:15 ` Petr Baudis
  2008-07-24 23:55   ` Donald Brady
  0 siblings, 1 reply; 3+ messages in thread
From: Petr Baudis @ 2008-07-24 23:15 UTC (permalink / raw)
  To: Donald Brady; +Cc: git

  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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: git newbie - cloning / check out help
  2008-07-24 23:15 ` Petr Baudis
@ 2008-07-24 23:55   ` Donald Brady
  0 siblings, 0 replies; 3+ messages in thread
From: Donald Brady @ 2008-07-24 23:55 UTC (permalink / raw)
  To: Petr Baudis; +Cc: git

Hi Peter.

I got it working now thanks to your pointer.

Donald

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

>  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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-07-25  0:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-24 21:24 git newbie - cloning / check out help Donald Brady
2008-07-24 23:15 ` Petr Baudis
2008-07-24 23:55   ` Donald Brady

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox