From: Junio C Hamano <gitster@pobox.com>
To: Marius Storm-Olsen <marius@trolltech.com>
Cc: Marius Storm-Olsen <git@storm-olsen.com>,
spearce@spearce.org, git@vger.kernel.org
Subject: Re: [PATCH] Add bare repository indicator for __git_ps1
Date: Sun, 22 Feb 2009 08:49:13 -0800 [thread overview]
Message-ID: <7v63j22z92.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 49A05958.7050703@trolltech.com
Marius Storm-Olsen <marius@trolltech.com> writes:
>> 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.
next prev parent reply other threads:[~2009-02-22 16:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 14:48 [PATCH] Add bare repository indicator for __git_ps1 Marius Storm-Olsen
2009-02-21 14:53 ` Marius Storm-Olsen
2009-02-21 19:29 ` Junio C Hamano
2009-02-21 19:43 ` Marius Storm-Olsen
2009-02-22 16:49 ` Junio C Hamano [this message]
2009-02-23 7:52 ` Marius Storm-Olsen
2009-02-23 15:42 ` Shawn O. Pearce
2009-02-23 16:03 ` Marius Storm-Olsen
2009-02-23 16:16 ` Shawn O. Pearce
2009-02-23 18:55 ` Marius Storm-Olsen
2009-02-24 1:35 ` Junio C Hamano
2009-02-24 14:25 ` Ted Pavlic
2009-02-24 14:46 ` Marius Storm-Olsen
2009-02-24 15:39 ` Ted Pavlic
2009-02-24 17:01 ` Junio C Hamano
2009-02-24 19:47 ` Marius Storm-Olsen
2009-02-25 6:08 ` Junio C Hamano
2009-02-25 6:46 ` Marius Storm-Olsen
-- strict thread matches above, loose matches on Subject: below --
2009-02-20 14:56 Marius Storm-Olsen
2009-02-20 16:35 ` Johannes Schindelin
2009-02-20 16:46 ` Thomas Rast
2009-02-20 17:13 ` Michael J Gruber
2009-02-20 22:04 ` Marius Storm-Olsen
2009-02-20 16:39 ` Michael J Gruber
2009-02-20 21:55 ` Marius Storm-Olsen
2009-02-20 17:06 ` Ted Pavlic
2009-02-20 22:00 ` Marius Storm-Olsen
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=7v63j22z92.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@storm-olsen.com \
--cc=git@vger.kernel.org \
--cc=marius@trolltech.com \
--cc=spearce@spearce.org \
/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).