Re: [PATCH] Add bare repository indicator for __git_ps1

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 22, 2009, 16:49 UTC
Message-ID: <7v63j22z92.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <49A05958.7050703@trolltech.com>

Marius Storm-Olsen <marius@trolltech.com> writes:

Show 20 quoted lines

>> For doing any usual work of growing history, you would work inside
>> a repository with an work tree.  The only occasion you would *go*
>> to a bare repository would be to tweak, futz with and fix one that
>> is used as a distribution point, isn't it?  You usually update such
>> a repository by pushing into it, so your being there would be a
>> result of very conscious act of chdir'ing into it yourself, and you
>> wouldn't be spending too much time in there anyway.
>>
>> There may be a different workflow where you would stay in a bare
>> repository for an extended period of time and you would benefit
>> from such a reminder like this patch adds, but I do not think of
>> one.
>>
>> Care to enlighten?
>
> Right, I have quite a few repos on my machine which are just bare, as I
> use them gather branches and push out
> again. (http://repo.or.cz/w/git/platforms.git is one of them) However,
> it's probably just me, since I could just as easily put them in a proper
> directory structure to indicate their bareness.

Ah, so "gather branches and push out again" would look something like this?

    $ cd /pub/some/where/platforms.git
    $ git fetch platform1 ;# perhaps with master:one/master mapping
    $ git fetch platform2 ;# perhaps with master:two/master
    $ git push public

Then it is very understandable that you would spend time inside a bare repository. I do not understand the need for GIT_DIR! thing even less, but since we have that there already, I do not see a reason not to add this to the queue.