From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Renaming a repo
Date: Tue, 19 Apr 2011 11:32:04 -0700 [thread overview]
Message-ID: <BANLkTimeufOo1eLESqooaf+zN+16+mUJCA@mail.gmail.com> (raw)
In-Reply-To: <4DADD0C4.4010106@dbservice.com>
On 19 April 2011 11:13, Tomas Carnecky <tom@dbservice.com> wrote:
> On 4/19/11 8:02 PM, Hilco Wijbenga wrote:
>> 1. The current repo is 'abc.git'
>> 2. git clone abc.git
>
> git clone --mirror abc.git
>>
>> 3. Create new hosted repo 'xyz.git'
>
> cd abc; git push --mirror xyz.git
>
> then you are done.
Wow ... stunned silence ... :-) *That* was easy. I didn't realize I
could work with bare repos like that.
The more I use Git, the more I like it and the more impressed I am.
prev parent reply other threads:[~2011-04-19 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 18:02 Renaming a repo Hilco Wijbenga
2011-04-19 18:13 ` Tomas Carnecky
2011-04-19 18:32 ` Hilco Wijbenga [this message]
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=BANLkTimeufOo1eLESqooaf+zN+16+mUJCA@mail.gmail.com \
--to=hilco.wijbenga@gmail.com \
--cc=git@vger.kernel.org \
--cc=tom@dbservice.com \
/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 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 NNTP newsgroup(s).