From: Pierre Habouzit <madcoder@debian.org>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Use parseopts in builtin-fetch
Date: Mon, 05 Nov 2007 09:43:33 +0100 [thread overview]
Message-ID: <20071105084333.GA25574@artemis.corp> (raw)
In-Reply-To: <Pine.LNX.4.64.0711042233590.7357@iabervon.org>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On Mon, Nov 05, 2007 at 03:35:34AM +0000, Daniel Barkalow wrote:
> Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
> ---
> I mostly did this and the next one for practice with the API. I'm
> impressed that "git fetch -vv" is even handled correctly without anything
> special. Now that I've done it, assuming I did it right, it might as well
> get added to the series.
I believe the same patches (or very similar ones) are in pu but are
not in next yet because they conflict with the builtin-fetch recent
series.
see http://git.madism.org/?p=git.git;a=blobdiff;f=builtin-fetch.c;h=12b1c4;hp=6b1750d;hb=7407915;hpb=61610e6
> + OPT_BOOLEAN('q', "quiet", &quiet, "fetch silently"),
there is an OPT__QUIET(&quiet) for this one.
> + i = 1;
> if (i < argc) {
> int j = 0;
> refs = xcalloc(argc - i + 1, sizeof(const char *));
this is wrong, you meant i = 0, and frankly, it's better to just strip
i altogether.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-05 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 3:35 [PATCH] Use parseopts in builtin-fetch Daniel Barkalow
2007-11-05 8:43 ` Pierre Habouzit [this message]
2007-11-05 17:14 ` Daniel Barkalow
2007-11-05 8:55 ` Pierre Habouzit
2007-11-05 17:02 ` Kristian Høgsberg
2007-11-05 17:41 ` Daniel Barkalow
2007-11-05 19:13 ` Junio C Hamano
2007-11-05 19:48 ` Pierre Habouzit
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=20071105084333.GA25574@artemis.corp \
--to=madcoder@debian.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.