Re: GIT_ONE_FILESYSTEM inclusion?

From: Alex Riesen <raa.lkml@gmail.com>
Date: Mar 24, 2010, 13:59 UTC
Message-ID: <81b0412b1003240659u4e6de405t7750b66ca9292cdc@mail.gmail.com>
In-Reply-To: <20100324134048.GB10190@pixar.com>

On Wed, Mar 24, 2010 at 14:40, Lars Damerow <lars@pixar.com> wrote:

Show 8 quoted lines

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

Right. OTOH, if you know that your .git is accessible (on the right filesystem), but want to avoid scans in the directories below the top- level working directory (submodules?), you may want to have it configurable per-repository. The environment variable will affect scan in all your repositories you visit in this session, which maybe what you want, and maybe not. And yes, the config option is also in addition to, not instead of the environment variable.

Show 5 quoted lines

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

Oh, I wasn't clear. I didn't mean "instead of". A command-line option _in_addition_ to the environment variable. For one-off uses.