From: Felipe Contreras <felipe.contreras@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3 01/10] config: Codestyle cleanups.
Date: Wed, 18 Feb 2009 11:18:33 +0200 [thread overview]
Message-ID: <94a0d4530902180118j4746a690q7a42ea087e23488@mail.gmail.com> (raw)
In-Reply-To: <bd6139dc0902170833r7e6672f4p831dacb2ed841b32@mail.gmail.com>
On Tue, Feb 17, 2009 at 6:33 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Tue, Feb 17, 2009 at 14:52, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
>
> Did I miss 0/10 somehow? If not, it would be nice to have one if you
> send a long patch series :). That way I can ignore v3 of the series if
> the cover letter tells me nothing significant (to me) has changed. 1
> minutes to write for you, saves 5 minutes for all reviewers :).
Hmm, right. I was thinking on Junio and Johanness that already know
the context, so they don't need an introduction, but I forgot about
other people that might be interested in giving this a review.
In any case, this patch series is a try to re-organize the code of
'git config' and the main change is to use parseopt for better
maintainability and option parsing. A few functionality changes are
provided, like the fact that now the arguments don't need to be in a
specific order: (--global -l vs -l --global), and improvements in
error reporting. Otherwise it should work exactly the same as before
(except with a much better --help).
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2009-02-18 9:20 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
2009-02-17 16:33 ` [PATCH v3 01/10] config: Codestyle cleanups Sverre Rabbelier
2009-02-18 9:18 ` Felipe Contreras [this message]
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=94a0d4530902180118j4746a690q7a42ea087e23488@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@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.
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).