From: Duy Nguyen <pclouds@gmail.com>
To: Kevin D <me@ikke.info>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: how to make "full" copy of a repo
Date: Mon, 30 Mar 2015 22:22:07 +0700 [thread overview]
Message-ID: <CACsJy8AN6X3oh2=yLn-szEApEMC+uQMmO6qBYbPrVNK1_d5tEQ@mail.gmail.com> (raw)
In-Reply-To: <20150328143152.GB9387@vps892.directvps.nl>
On Sat, Mar 28, 2015 at 9:31 PM, Kevin D <me@ikke.info> wrote:
> Git clone is never going to get you a copy where nothing is lost.
>
> What you are losing on clone is:
>
> * config settings (this includes the configures remotes)
> * hooks
> * reflog (history of refs, though, by default disabled for bare
> repositories)
> * 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)
This is true. But I wonder if we should (and can) support
--super-mirror option (disabled by default), where reflog and stashes
are kept, for backup purposes. We might keep unreferenced objects as
well if it's not hard to do.
--
Duy
next prev parent reply other threads:[~2015-03-30 15:22 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
2015-03-29 11:05 ` Kevin D
2015-03-30 15:22 ` Duy Nguyen [this message]
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
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='CACsJy8AN6X3oh2=yLn-szEApEMC+uQMmO6qBYbPrVNK1_d5tEQ@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=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.
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).