From: Jakub Narebski <jnareb@gmail•com>
To: Ping Yin <pkufranky@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 10:18:58 +0200 [thread overview]
Message-ID: <201005081018.59757.jnareb@gmail.com> (raw)
In-Reply-To: <u2p46dff0321005071930n21de08bcv62d88377f082521@mail.gmail.com>
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.
From mentioned backward-incompatibile proposals, there is one that is
already used (at least in some Perl modules in CPAN), namely
[@foo]
syntax, which is used by Dist::Zilla (where 'foo' is name of "bundle",
which roughly means set of pre-defined configuration variables).
Although it does not support globbing...
The '@INCLUDE = db_config.ini' is taken from OpenInteract2::Config::Ini.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-05-08 8:19 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 [this message]
2010-05-08 9:03 ` Ping Yin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201005081018.59757.jnareb@gmail.com \
--to=jnareb@gmail$(echo .)com \
--cc=avarab@gmail$(echo .)com \
--cc=eli@barzilay$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=hvoigt@hvoigt$(echo .)net \
--cc=pkufranky@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