From: Andres Freund <andres@anarazel.de>
To: michael.meeks@novell.com
Cc: Brian Gernhardt <benji@silverinsanity.com>,
git@vger.kernel.org, kendy@novell.com,
Norbert Thiebaud <nthiebaud@gmail.com>
Subject: Re: copying git repositories ...
Date: Mon, 28 Feb 2011 16:03:08 +0100 [thread overview]
Message-ID: <201102281603.08375.andres@anarazel.de> (raw)
In-Reply-To: <1298903102.14697.127.camel@lenovo-w500>
Hi Michael,
On Monday, February 28, 2011 03:25:02 PM Michael Meeks wrote:
> Hi Andres & Brian,
> For #2 - I would use the verb 'clone' except of course the 'clone' I'm
> talking about would be one that is identical, the same, with no
> differences (not eg. missing a few limbs ;-)
>
> Clearly cp -lR is bad & evil and all that; but it yields exactly what I
> need to effectively manage my local trees, multiple checkouts, and
> different builds without burning the entire disk.
>
> Is there a blessed 'cp -lR' wrapper for git that is functionally
> identical ? [ and I'm happy of course for some slow divergence, and loss
> of efficiency as I pull more changes from time to time into each tree ].
What about git clone --reference=oldrepo ssh://upstream/ ?
Andres
next prev parent reply other threads:[~2011-02-28 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:34 libreoffice merge(tool?) issue #3 Michael Meeks
2011-02-22 15:55 ` Brian Gernhardt
2011-02-24 16:39 ` libreoffice merge(tool?) issue #3 ... (bogus) Michael Meeks
2011-02-25 10:08 ` Michael J Gruber
2011-02-25 20:55 ` Andres Freund
2011-02-28 14:25 ` copying git repositories Michael Meeks
2011-02-28 15:03 ` Andres Freund [this message]
2011-02-28 15:10 ` Brian Gernhardt
2011-02-22 17:30 ` libreoffice merge(tool?) issue #3 Michael J Gruber
2011-02-22 18:14 ` Michael Meeks
2011-02-23 11:18 ` Michael J Gruber
2011-02-23 13:22 ` Michael J Gruber
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=201102281603.08375.andres@anarazel.de \
--to=andres@anarazel.de \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=kendy@novell.com \
--cc=michael.meeks@novell.com \
--cc=nthiebaud@gmail.com \
/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).