From: David Kastrup <dak@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Git question. Is there a way of duplicating a git repository?
Date: Mon, 16 Nov 2015 09:42:02 +0100 [thread overview]
Message-ID: <87ziyejpyd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20151114213550.GA2995@acm.fritz.box> (Alan Mackenzie's message of "Sat, 14 Nov 2015 21:35:50 +0000")
Alan Mackenzie <acm@muc.de> writes:
> Hello, John.
>
> On Sat, Nov 14, 2015 at 10:17:33AM -0800, John Wiegley wrote:
>> >>>>> Alan Mackenzie <acm@muc.de> writes:
>
>> > So, is there any convenient way of duplicating a repo (using hard links, and
>> > preserving config info)?
>
>> A clone on the same device uses hard-links by default.
>
> But what git calls a "clone" is not a duplicate repo. It is radically
> different from the original. In particular, the new repo's "remote
> origin" is set to the original repo; I want it to duplicate what the
> original repo had set.
git clone --mirror
Curiously, this implies --bare but you can just edit the config file
afterwards and remove the `bare' setting.
--
David Kastrup
next prev parent reply other threads:[~2015-11-16 8:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 11:20 Git question. Is there a way of duplicating a git repository? Alan Mackenzie
2015-11-14 17:03 ` Achim Gratz
2015-11-14 17:06 ` Dmitry Gutov
2015-11-15 10:43 ` Alan Mackenzie
2015-11-14 17:20 ` Liang Wang
2015-11-14 17:27 ` Ivan Shmakov
2015-11-14 17:37 ` David Reitter
2015-11-14 17:57 ` chris.nixon
2015-11-14 18:17 ` John Wiegley
2015-11-14 21:35 ` Alan Mackenzie
2015-11-16 8:42 ` David Kastrup [this message]
2015-11-17 11:54 ` Stephen Leake
2015-11-14 19:21 ` Andreas Schwab
2015-11-14 20:02 ` Andy Moreton
2015-11-14 21:02 ` Ken Brown
2015-11-15 10:33 ` Alan Mackenzie
2015-11-15 2:46 ` Mike Gerwitz
2015-11-15 7:58 ` Paul Eggert
2015-11-15 10:02 ` Steinar Bang
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ziyejpyd.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).