From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [RFC/WIP 0/3] Shared config
Date: Thu, 9 Dec 2010 22:09:45 +0700 [thread overview]
Message-ID: <1291907388-9068-1-git-send-email-pclouds@gmail.com> (raw)
Another approach is [1]. I think this one is somewhat simpler and
exposes less risk by putting the shared config under version control.
This is not complete (for example, git-prune should learn about this),
but is there any serious flaw that I missed?
One thing that I haven't thought of is the shared config between
subprojects. Maybe there's a better approach for subprojects.
(The resistance to nd/struct-pathspec seems great. This is the second
time I come to address it and end up with something else)
[1] http://thread.gmane.org/gmane.comp.version-control.git/162309
Nguyễn Thái Ngọc Duy (3):
config: read full file content before parsing
config: add git_config_from_sha1() to read from a blob
config: add core.sharedconfig
cache.h | 1 +
config.c | 110 +++++++++++++++++++++++++++++++++++++++++++--------------
environment.c | 1 +
3 files changed, 85 insertions(+), 27 deletions(-)
--
1.7.3.3.476.g893a9
next reply other threads:[~2010-12-09 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 15:09 Nguyễn Thái Ngọc Duy [this message]
2010-12-09 15:09 ` [PATCH 1/3] config: read full file content before parsing Nguyễn Thái Ngọc Duy
2010-12-09 15:09 ` [PATCH 2/3] config: add git_config_from_sha1() to read from a blob Nguyễn Thái Ngọc Duy
2010-12-09 15:58 ` Thiago Farina
2010-12-09 17:02 ` Jonathan Nieder
2010-12-09 15:09 ` [PATCH 3/3] config: add core.sharedconfig Nguyễn Thái Ngọc Duy
2010-12-09 16:00 ` Thiago Farina
2010-12-10 1:53 ` Nguyen Thai Ngoc Duy
2010-12-09 18:13 ` Junio C Hamano
2010-12-09 18:19 ` Jonathan Nieder
2010-12-10 1:29 ` Nguyen Thai Ngoc Duy
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=1291907388-9068-1-git-send-email-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
/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).