git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Andreas Krey <a.krey@gmx.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Priming git clone with a local repo?
Date: Thu, 11 Jul 2013 09:01:15 -0700	[thread overview]
Message-ID: <7vtxk1rsqc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130711093532.GA28255@inner.h.apk.li> (Andreas Krey's message of "Thu, 11 Jul 2013 11:35:32 +0200")

Andreas Krey <a.krey@gmx.de> writes:

> I'm wondering if there is (or will be) a way of doing almost
>
>   git clone --reference localrepo host:canonrep
>
> Basically, I don't want the implications of --reference but still the
> performance advantages of reusing local objects/pack files.

I think the standard operating procedure for that is to still clone
with the "--reference" option first, and then do "repack -a -d" in
the resulting clone (note the lack of "-l" option in "repack").

After that repack, you should be able to discard the alternates
file.

    $ git clone --reference ../there otherhost:repo ours.git
    $ cd ours.git
    $ git repack -a -d ;# no "-l"!!!
    $ mv .git/objects/info/alternates .git/objects/info/alter-nates
    $ git fsck
    $ rm .git/objects/info/alter-nates

  reply	other threads:[~2013-07-11 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  3:03 A local shared clone is now much slower Stephen Rothwell
2013-07-08  3:20 ` Duy Nguyen
2013-07-08  4:25   ` Stephen Rothwell
2013-07-08  7:30 ` Jeff King
2013-07-08  8:57   ` Duy Nguyen
2013-07-08 15:00     ` Junio C Hamano
2013-07-09  4:30       ` Jeff King
2013-07-11  9:35       ` Priming git clone with a local repo? Andreas Krey
2013-07-11 16:01         ` Junio C Hamano [this message]
2013-07-08 13:05   ` A local shared clone is now much slower Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vtxk1rsqc.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=a.krey@gmx.de \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).