From: Benjamin LaHaise <bcrl@kvack.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git clone does not work with GIT_OBJECT_DIRECTORY set
Date: Tue, 7 Mar 2006 11:13:28 -0500 [thread overview]
Message-ID: <20060307161328.GA5410@kvack.org> (raw)
In-Reply-To: <7vu0aa4vj4.fsf@assigned-by-dhcp.cox.net>
On Mon, Mar 06, 2006 at 10:29:51PM -0800, Junio C Hamano wrote:
> I think the recommended way these days to set up multiple
> repositories that work on related projects is to set up a single
> clone from external source (e.g. linux-2.6.git), and make a set
> of local "-l -s" clones out of it, and then fetch forked
> upstreams into them. It would go something like this:
I had been doing that, but it's gotten too painful to keep everything in
sync. Sigh.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <dont@kvack.org>.
prev parent reply other threads:[~2006-03-07 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 1:21 git clone does not work with GIT_OBJECT_DIRECTORY set Benjamin LaHaise
2006-03-06 1:33 ` Junio C Hamano
2006-03-06 1:38 ` Benjamin LaHaise
2006-03-07 6:29 ` Junio C Hamano
2006-03-07 16:13 ` Benjamin LaHaise [this message]
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=20060307161328.GA5410@kvack.org \
--to=bcrl@kvack.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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;
as well as URLs for NNTP newsgroup(s).