From: Sitaram Chamarty <sitaramc@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Tim Visher <tim.visher@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Make a non-bare repo bare.
Date: Thu, 16 Jul 2009 17:09:37 +0530 [thread overview]
Message-ID: <2e24e5b90907160439i29171e9fka3baf6bf871a6011@mail.gmail.com> (raw)
In-Reply-To: <7vbpnlbbln.fsf@alter.siamese.dyndns.org>
On Thu, Jul 16, 2009 at 8:03 AM, Junio C Hamano<gitster@pobox.com> wrote:
> Tim Visher <tim.visher@gmail.com> writes:
>
>> Hello Everyone,
>>
>> I recently had occasion to make a previously non-bare repo bare. Is
>> there any way to do this? It will not allow me to delete a branch
>> that I'm on so I wasn't sure how to proceed.
>
> Funny.
>
> http://article.gmane.org/gmane.comp.version-control.git/123303
>
> It is posed as a question but describes the correct (and officially
> supported) procedure.
The linked procedure uses git clone --bare. It is my belief (and
please correct me if I'm wrong) that only a git clone --mirror
actually does what you want here -- a mere "bare" clone would lose
your remotes and their tracking branches would it not?
If I'm wrong please correct me...
next prev parent reply other threads:[~2009-07-16 11:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 21:43 Make a non-bare repo bare Tim Visher
2009-07-15 21:48 ` Paolo Bonzini
2009-07-16 0:54 ` Tim Visher
2009-07-16 2:19 ` Jeff King
2009-07-16 2:33 ` Junio C Hamano
2009-07-16 8:51 ` Graeme Geldenhuys
2009-07-16 8:55 ` Mike Ralphson
2009-07-16 20:47 ` Junio C Hamano
2009-07-17 3:59 ` Sitaram Chamarty
2009-07-16 11:39 ` Sitaram Chamarty [this message]
2009-07-16 11:47 ` Tim Visher
2009-07-16 20:51 ` Junio C Hamano
2009-07-17 1:20 ` Sitaram Chamarty
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=2e24e5b90907160439i29171e9fka3baf6bf871a6011@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tim.visher@gmail.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).