From: David Aguilar <davvid@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Johannes Sixt <j.sixt@viscovery.net>,
Lars Damerow <lars@pixar.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>
Subject: Re: GIT_ONE_FILESYSTEM inclusion?
Date: Sat, 27 Mar 2010 15:27:32 -0700 [thread overview]
Message-ID: <20100327222730.GA10922@gmail.com> (raw)
In-Reply-To: <vpqd3yt4yyp.fsf@bauges.imag.fr>
On Wed, Mar 24, 2010 at 02:43:26PM +0100, Matthieu Moy wrote:
> 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/
Right.
As this thread showed, we can't have a config option for this
feature. Were there any other objections to the patch?
It looks good to me.
Peff also agreed that it was an overall improvement.
http://thread.gmane.org/gmane.comp.version-control.git/142262
Thread with the latest (v3) version of the patch:
http://thread.gmane.org/gmane.comp.version-control.git/142436
We could use this feature at Disney Animation as well.
We maintain a list of $GIT_CEILING_DIRECTORIES and could do
without having to maintain it if we had this feature.
Plus, Lars is one of the git users that doesn't even flinch when
the Perforce servers at Pixar get a hiccup, so we should try and
help our fellow "renegade" git users ;-)
--
David
next prev parent reply other threads:[~2010-03-27 22:27 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
2010-03-27 22:27 ` David Aguilar [this message]
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=20100327222730.GA10922@gmail.com \
--to=davvid@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=lars@pixar.com \
--cc=peff@peff.net \
--cc=raa.lkml@gmail.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).