From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Lars Damerow <lars@pixar.com>,
Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org
Subject: Re: GIT_ONE_FILESYSTEM inclusion?
Date: Wed, 24 Mar 2010 20:07:03 +0100 [thread overview]
Message-ID: <81b0412b1003241207s4951b32cpbe105e7b3623f61a@mail.gmail.com> (raw)
In-Reply-To: <7vpr2tu1bd.fsf@alter.siamese.dyndns.org>
On Wed, Mar 24, 2010 at 17:33, Junio C Hamano <gitster@pobox.com> wrote:
> Alex Riesen <raa.lkml@gmail.com> writes:
>
>> 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.
>
> I may have been the one who mentioned "-x to git potty" as a possibility,
> but I agree with Lars---I think it would be too cumbersome to use in
> practice.
>
> When would you invoke this feature as "one-off"?
>
Maybe when I want to make sure git status does not go all over an
NFS mounted submodule.
But frankly, I think it will be the most obscure feature of Git ever,
with a command-line option or without. I just wanted to suggest
(and actually, just should have, stupid me) to keep it in line with
other similar configurations, which are present in all three forms
(work tree comes to mind... Come to think of it, only the work tree).
next prev parent reply other threads:[~2010-03-24 19:07 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
2010-03-24 13:59 ` Alex Riesen
2010-03-24 16:33 ` Junio C Hamano
2010-03-24 19:07 ` Alex Riesen [this message]
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=81b0412b1003241207s4951b32cpbe105e7b3623f61a@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=lars@pixar.com \
/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).