From: Ping Yin <pkufranky@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git <git@vger.kernel.org>, "Eli Barzilay" <eli@barzilay.org>,
"Heiko Voigt" <hvoigt@hvoigt.net>
Subject: Re: [PATCH/RFC] Hacky version of a glob() driven config include
Date: Sat, 8 May 2010 17:03:15 +0800 [thread overview]
Message-ID: <r2i46dff0321005080203m65cb8acak750f4ef46bf4d6e8@mail.gmail.com> (raw)
In-Reply-To: <201005081018.59757.jnareb@gmail.com>
On Sat, May 8, 2010 at 4:18 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>
> On Sat, 8 May 2010, Ping Yin wrote:
> > >
> > > But perhaps we can break backwards compatibility here. I don't know...
> > >
> > I think we can. Because config file is not in repository, so if your
> > older git doesn't support it, you should not use this new syntax.
>
> Actually per-repository $GIT_DIR/config file *is* in repository... but
> is not distributed (it is not transferred on clone / fetch).
>
> The problem with breaking backwards compatibility is when repository is
> on shared filesystem (be it networked filesystem such as NFS or
> CIFS/Samba share, or portable USB (pen)drive), and can be accessed by
> different versions of git.
You are right, i missed this case.
However, If NFS is used, the git version is very likely the same. So i
think this case is not worth the effort to keep the backwards
compatibility.
>
> The '@INCLUDE = db_config.ini' is taken from OpenInteract2::Config::Ini.
I prefer "include foo" which is used by apache, and "@include foo"
which doesn't fail to parse when foo doesn't exist.
next prev parent reply other threads:[~2010-05-08 9:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 21:20 Is there interest in reading ~/.gitconfig.d/* and /etc/gitconfig.d/*? Ævar Arnfjörð Bjarmason
2010-04-01 22:03 ` Heiko Voigt
2010-04-04 7:24 ` Peter Krefting
2010-04-04 7:59 ` Eli Barzilay
[not found] ` <19384.17579.205005.86711@winooski.ccs.neu.edu>
2010-04-06 8:15 ` Ævar Arnfjörð Bjarmason
2010-04-06 9:02 ` Jakub Narebski
2010-05-06 21:14 ` [PATCH/RFC] Hacky version of a glob() driven config include Ævar Arnfjörð Bjarmason
2010-05-07 6:00 ` Bert Wesarg
2010-05-07 16:56 ` Ævar Arnfjörð Bjarmason
2010-05-07 18:29 ` Bert Wesarg
2010-05-07 18:58 ` Ævar Arnfjörð Bjarmason
2010-05-07 19:02 ` Jacob Helwig
2010-05-07 19:52 ` Bert Wesarg
2010-05-07 20:11 ` [PATCH/RFC v2] " Ævar Arnfjörð Bjarmason
2010-05-07 20:46 ` [PATCH/RFC] " Jakub Narebski
2010-05-07 22:15 ` Ævar Arnfjörð Bjarmason
2010-05-07 23:43 ` Jakub Narebski
2010-05-08 2:30 ` Ping Yin
2010-05-08 8:18 ` Jakub Narebski
2010-05-08 9:03 ` Ping Yin [this message]
2010-05-08 5:06 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=r2i46dff0321005080203m65cb8acak750f4ef46bf4d6e8@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=avarab@gmail.com \
--cc=eli@barzilay.org \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=jnareb@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).