From: Casey Dahlin <cdahlin@redhat.com>
To: Grant Erickson <gerickson@nuovations.com>
Cc: git@vger.kernel.org
Subject: Re: GIT and Cloning Remote Repositories into "Local Remote" Repositories
Date: Mon, 27 Sep 2010 11:18:08 -0400 [thread overview]
Message-ID: <20100927151807.GE31809@foucault.redhat.com> (raw)
In-Reply-To: <C8C53EC9.1E621%gerickson@nuovations.com>
On Sun, Sep 26, 2010 at 06:17:45PM -0700, Grant Erickson wrote:
> On 9/20/10 6:37 PM, Casey Dahlin wrote:
> > On Mon, Sep 20, 2010 at 06:22:09PM -0700, Grant Erickson wrote:
> >> Perhaps 'submodules' are what I am looking for?
> >>
> >
> > Yup, exactly :) the manpage git submodule should get you going.
>
> Casey:
>
> Thanks for the prompt reply.
>
> I spent some time over the weekend playing with the various submodule
> tutorials and I wasn't left feeling convinced that it's the right solution,
> particularly with the added complexity around commits and pushes (trailing
> slashes, etc.) that I am sure my users are going to get wrong more often
> than right.
>
*snip*
>
> And so on for the linux subtree as well. Any further tips or course
> corrections you can offer, particularly relative to subtree merges?
>
Unfortunately I'm not an expert here. I know what submodules do but I haven't
used them much (in fact I last looked at them just after they were introduced.
They were even rougher back then).
I may have missed it but if you haven't I'd update the list on all of this
again.
--CJD
next prev parent reply other threads:[~2010-09-27 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 1:22 GIT and Cloning Remote Repositories into "Local Remote" Repositories Grant Erickson
2010-09-21 1:37 ` Casey Dahlin
2010-09-27 1:17 ` Grant Erickson
2010-09-27 15:18 ` Casey Dahlin [this message]
2010-09-27 15:29 ` Grant Erickson
2010-09-21 4:26 ` Tay Ray Chuan
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=20100927151807.GE31809@foucault.redhat.com \
--to=cdahlin@redhat.com \
--cc=gerickson@nuovations.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.