From: Heiko Voigt <hvoigt@hvoigt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Jens Lehmann <jens.lehmann@web.de>,
Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Subject: [PATCH v5 0/5] allow more sources for config values
Date: Fri, 12 Jul 2013 00:36:14 +0200 [thread overview]
Message-ID: <20130711223614.GA26477@book-mint> (raw)
Hi,
I finally got around rerolling this series.
The fourth iteration can be found here[1]. You can also find these patches as a
branch on my github[2].
There is not many changes since the last iteration. I have added some
documentation for the --blob option and now there is no rename of the
do_config_from() function anymore.
Cheers Heiko
[1] http://article.gmane.org/gmane.comp.version-control.git/223964
[2] https://github.com/hvoigt/git/commits/hv/strbuf_config_parsing-series5
Heiko Voigt (5):
config: factor out config file stack management
config: drop cf validity check in get_next_char()
config: make parsing stack struct independent from actual data source
teach config --blob option to parse config from database
do not die when error in config parsing of buf occurs
Documentation/git-config.txt | 7 ++
builtin/config.c | 31 ++++++-
cache.h | 6 +-
config.c | 217 +++++++++++++++++++++++++++++++++----------
t/t1307-config-blob.sh | 70 ++++++++++++++
5 files changed, 278 insertions(+), 53 deletions(-)
create mode 100755 t/t1307-config-blob.sh
--
1.8.3.2.773.gcfaae5b
next reply other threads:[~2013-07-11 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 22:36 Heiko Voigt [this message]
2013-07-11 22:40 ` [PATCH v5 1/5] config: factor out config file stack management Heiko Voigt
2013-07-11 22:43 ` [PATCH v5 2/5] config: drop cf validity check in get_next_char() Heiko Voigt
2013-07-11 22:44 ` [PATCH v5 3/5] config: make parsing stack struct independent from actual data source Heiko Voigt
2013-07-11 22:46 ` [PATCH v5 4/5] teach config --blob option to parse config from database Heiko Voigt
2013-07-11 22:48 ` [PATCH v5 5/5] do not die when error in config parsing of buf occurs Heiko Voigt
2013-07-11 23:26 ` [PATCH v5 0/5] allow more sources for config values Junio C Hamano
2013-07-12 10:10 ` 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=20130711223614.GA26477@book-mint \
--to=hvoigt@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jens.lehmann@web.de \
--cc=peff@peff.net \
--cc=ramsay@ramsay1.demon.co.uk \
/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).