From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Kevin D <me@ikke.info>
Cc: git@vger.kernel.org
Subject: Re: how to make "full" copy of a repo
Date: Sun, 29 Mar 2015 04:21:26 +0200 [thread overview]
Message-ID: <1427595686.4912.17.camel@scientia.net> (raw)
In-Reply-To: <20150328143152.GB9387@vps892.directvps.nl>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Sat, 2015-03-28 at 15:31 +0100, Kevin D wrote:
> What you are losing on clone is:
> * config settings (this includes the configures remotes)
> * hooks
that would be okay...
> * reflog (history of refs, though, by default disabled for bare
> repositories)
is there a way to get this copied?
> * Stashes, because the reference to them is stored in the reflog
> * unreferenced objects (though you said those are not a requirement, it
> is still something that is lost)
that would be okay for me either.
> git clone --mirror is used for repositories that regularly get updates
> from the repositories they were cloned from. Though this is not what you
> want, it's not difficult to reset the refspecs to the default refspecs.
What do you mean here? What would I need to reset exactly?
> git clone --mirror is the closest you are going to get by only using
> git.
I see, thanks :)
> So to summarize, git clone is only used for cloning history, which means
> objects and refs, the rest is not part of cloning. To get more, you have
> to go outside git.
Thanks :)
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-03-29 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 2:56 how to make "full" copy of a repo Christoph Anton Mitterer
2015-03-28 14:31 ` Kevin D
2015-03-29 2:21 ` Christoph Anton Mitterer [this message]
2015-03-29 11:05 ` Kevin D
2015-03-30 15:22 ` Duy Nguyen
2015-03-30 17:37 ` Junio C Hamano
2015-03-28 18:52 ` Torsten Bögershausen
2015-03-28 20:33 ` Ævar Arnfjörð Bjarmason
2015-03-29 2:22 ` Christoph Anton Mitterer
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=1427595686.4912.17.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=git@vger.kernel.org \
--cc=me@ikke.info \
/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.