From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Alex Riesen <raa.lkml@gmail•com>
Cc: Johannes Sixt <j.sixt@viscovery•net>,
Lars Damerow <lars@pixar•com>,
git@vger•kernel.org
Subject: Re: GIT_ONE_FILESYSTEM inclusion?
Date: Wed, 24 Mar 2010 14:43:26 +0100 [thread overview]
Message-ID: <vpqd3yt4yyp.fsf@bauges.imag.fr> (raw)
In-Reply-To: <81b0412b1003240437n799bac07sb74db749d647817d@mail.gmail.com> (Alex Riesen's message of "Wed\, 24 Mar 2010 12\:37\:39 +0100")
Alex Riesen <raa.lkml@gmail•com> writes:
> On Wed, Mar 24, 2010 at 10:35, Johannes Sixt <j.sixt@viscovery•net> wrote:
>> Am 3/24/2010 10:29, schrieb Alex Riesen:
>>> And while at it, how about making it a config option? (i.e. core.oneFilesystem?)
>>
>> It's difficult to have this as a config option when you are looking for a
>> repository... ;)
>>
>
> Isn't it a little pointless to look for repository when you can't
> access its config?
I guess Johannes's point is that the config option can be in
$GIT_DIR/config, which you can't access when looking for $GIT_DIR.
OTOH, looking at ~/.gitconfig to find a core.oneFilesystem makes sense
(but is probably painfull to implement since the current code to parse
config file will look for $GIT_DIR first).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-03-24 13:43 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
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 [this message]
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=vpqd3yt4yyp.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=j.sixt@viscovery$(echo .)net \
--cc=lars@pixar$(echo .)com \
--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