From: Alan Mackenzie <acm@muc.de>
To: Ken Brown <kbrown@cornell.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Git question. Is there a way of duplicating a git repository?
Date: Sun, 15 Nov 2015 10:33:40 +0000 [thread overview]
Message-ID: <20151115103339.GB1766@acm.fritz.box> (raw)
In-Reply-To: <5647A163.5020302@cornell.edu>
Hello, Ken.
On Sat, Nov 14, 2015 at 04:02:27PM -0500, Ken Brown wrote:
> On 11/14/2015 6:20 AM, Alan Mackenzie wrote:
> > Hello, Emacs.
> > Now that we've cut the emacs-25 release branch, I'd like to have a
> > distinct repository for this.
> > I could simply download another copy from savannah, but this would
> > (presumably) be a distinct copy, rather than hard linking the repository
> > files. This would cost me disk (and backup) space.
> > Or I could clone my master repository to make emacs-25. But this would
> > make the new repo firmly subordinate to the master repo, rather than
> > directly with savannah.
> You can fix that by issuing the following command in the new repo:
> git remote set-url origin <userid>@git.sv.gnu.org:/srv/git/emacs.git master
> After doing that, you'll to do 'git pull' in order to bring in the remote branches, and then you can do 'git checkout emacs-25'.
First of all, many thanks for actually addressing the question I asked.
;-)
What I did in the end was to clone a new repo with the --mirror argument
(so as to copy all the branches, rather than creating new ones pointing
at the original repo), and manually edited .../.git/config so as to get
working directories. Then I changed the remote origin url in that file
by hand.
Having done "git checkout", I was then able to "git pull" from savannah,
and switch to branch emacs-25 with another "git checkout".
So, I'm where I want to be!
Thanks again.
> Ken
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-11-15 10:33 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
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 [this message]
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=20151115103339.GB1766@acm.fritz.box \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
/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).