Re: Make a non-bare repo bare.

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 16, 2009, 20:51 UTC
Message-ID: <7v8wio8i73.fsf@alter.siamese.dyndns.org>
In-Reply-To: <2e24e5b90907160439i29171e9fka3baf6bf871a6011@mail.gmail.com>

Sitaram Chamarty <sitaramc@gmail.com> writes:

Show 20 quoted lines

> 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?

Depends on "what you want here".

I assumed that the request was to set up the most typical use of a bare repository, that is to prepare a distribution point, separate from your primary working repository with a work tree, from which you push your updates into this new bare repository.

And in such a distribution point, you do not need nor want remotes. The point of remote tracking branches is to let you peek what others are doing and merge with them, and that is done while you advance your history in your primary working area with the work tree. It does not happen in your distribution point.