public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Lars Damerow <lars@pixar•com>
To: Alex Riesen <raa.lkml@gmail•com>
Cc: Johannes Sixt <j.sixt@viscovery•net>, git@vger•kernel.org
Subject: Re: GIT_ONE_FILESYSTEM inclusion?
Date: Wed, 24 Mar 2010 06:40:49 -0700	[thread overview]
Message-ID: <20100324134048.GB10190@pixar.com> (raw)
In-Reply-To: <81b0412b1003240437n799bac07sb74db749d647817d@mail.gmail.com>

>From Alex Riesen <raa.lkml@gmail•com>, Wed, Mar 24, 2010 at 12:37:39PM +0100:
> 
> Isn't it a little pointless to look for repository when you can't
> access its config?

If you're doing the trendy thing of putting repository information in
your shell prompt, then your prompt is looking for a repository every
time you change a directory.

As for making this a command-line option: that's certainly doable, but
it makes it harder to enforce the option's use across an organization.
It's far easier for me to set an environment variable centrally on a
thousand workstations than to convince a potentially large number of
users to set a new shell alias for git.

thanks,
-lars

--
lars r. damerow :: button pusher :: pixar animation studios

  reply	other threads:[~2010-03-24 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 23:20 GIT_ONE_FILESYSTEM inclusion? Lars Damerow
2010-03-24  9:29 ` Alex Riesen
2010-03-24  9:35   ` Johannes Sixt
2010-03-24 11:37     ` Alex Riesen
2010-03-24 13:40       ` Lars Damerow [this message]
2010-03-24 13:59         ` Alex Riesen
2010-03-24 16:33           ` Junio C Hamano
2010-03-24 19:07             ` Alex Riesen
2010-03-24 20:04               ` Junio C Hamano
2010-03-24 20:36                 ` Alex Riesen
2010-03-24 20:07               ` Lars Damerow
2010-03-24 13:43       ` Matthieu Moy
2010-03-27 22:27         ` David Aguilar
2010-03-28  9:24           ` Jeff King

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=20100324134048.GB10190@pixar.com \
    --to=lars@pixar$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=j.sixt@viscovery$(echo .)net \
    --cc=raa.lkml@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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