From: Petr Baudis <pasky@suse.cz>
To: Donald Brady <dbrady010@me.com>
Cc: git@vger.kernel.org
Subject: Re: git newbie - cloning / check out help
Date: Fri, 25 Jul 2008 01:15:31 +0200 [thread overview]
Message-ID: <20080724231531.GS32184@machine.or.cz> (raw)
In-Reply-To: <loom.20080724T211609-298@post.gmane.org>
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
next prev parent reply other threads:[~2008-07-24 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 21:24 git newbie - cloning / check out help Donald Brady
2008-07-24 23:15 ` Petr Baudis [this message]
2008-07-24 23:55 ` Donald Brady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080724231531.GS32184@machine.or.cz \
--to=pasky@suse.cz \
--cc=dbrady010@me.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox