From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH v3 03/10] config: Make git_config() more flexible
Date: Wed, 18 Feb 2009 14:01:38 -0800 [thread overview]
Message-ID: <7vvdr7tnel.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <94a0d4530902181330o298fce1am31d9d15145956d78@mail.gmail.com> (Felipe Contreras's message of "Wed, 18 Feb 2009 23:30:39 +0200")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> What I'm trying to do is "Make git_config() don't return an error when
> there's no repo config file if there are other config files
> available"... I thought there was no short way to say that =/
git_config(): not having a per-repo config file is not an error
Please drop the full-stop at the end of the Subject: line, by the way.
next prev parent reply other threads:[~2009-02-18 22:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 13:52 [PATCH v3 01/10] config: Codestyle cleanups Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 02/10] config: Cleanup editor action Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 03/10] config: Make git_config() more flexible Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 04/10] config: Trivial rename in preparation for parseopt Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 05/10] config: Reorganize get_color* Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 06/10] config: Use parseopt Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 07/10] config: Disallow --getcolor* and other actions Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 08/10] config: Disallow multiple config file locations Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 09/10] config: Disallow multiple variable types Felipe Contreras
2009-02-17 13:52 ` [PATCH v3 10/10] config: Don't allow extra arguments for -e or -l Felipe Contreras
2009-02-18 21:13 ` [PATCH v3 03/10] config: Make git_config() more flexible Junio C Hamano
2009-02-18 21:30 ` Felipe Contreras
2009-02-18 22:01 ` Junio C Hamano [this message]
2009-02-17 16:33 ` [PATCH v3 01/10] config: Codestyle cleanups Sverre Rabbelier
2009-02-18 9:18 ` Felipe Contreras
2009-02-18 19:02 ` Junio C Hamano
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=7vvdr7tnel.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=felipe.contreras@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).