From: "Carlos Rica" <jasampler@gmail.com>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] Make builtin-reset.c use parse_options.
Date: Sun, 2 Mar 2008 13:54:10 +0100 [thread overview]
Message-ID: <1b46aba20803020454v322f061bi4f34a737e9e2b7f3@mail.gmail.com> (raw)
In-Reply-To: <20080302094031.GA2973@steel.home>
On Sun, Mar 2, 2008 at 10:40 AM, Alex Riesen <raa.lkml@gmail.com> wrote:
> Carlos Rica, Sat, Mar 01, 2008 17:29:38 +0100:
>
> > @@ -169,40 +173,31 @@ static const char *reset_type_names[] = { "mixed", "soft", "hard", NULL };
> >
> > int cmd_reset(int argc, const char **argv, const char *prefix)
> > {
> > - int i = 1, reset_type = NONE, update_ref_status = 0, quiet = 0;
> > + int i = 0, reset_type = NONE, update_ref_status = 0, quiet = 0;
> > const char *rev = "HEAD";
> > unsigned char sha1[20], *orig = NULL, sha1_orig[20],
> > *old_orig = NULL, sha1_old_orig[20];
> > struct commit *commit;
> > char *reflog_action, msg[1024];
> > + struct option options[] = {
>
> "static const"?
>
>
"static const" what?
options? cmd_reset? reset_type_names?
next prev parent reply other threads:[~2008-03-02 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:29 [PATCH] Make builtin-reset.c use parse_options Carlos Rica
2008-03-02 2:53 ` Junio C Hamano
2008-03-02 12:37 ` Carlos Rica
2008-03-02 16:18 ` Junio C Hamano
2008-03-03 14:07 ` Carlos Rica
2008-03-03 17:07 ` Pierre Habouzit
2008-03-03 22:40 ` Junio C Hamano
2008-03-04 9:45 ` Pierre Habouzit
2008-03-02 16:32 ` Johannes Schindelin
2008-03-02 9:40 ` Alex Riesen
2008-03-02 12:54 ` Carlos Rica [this message]
2008-03-02 15:55 ` Alex Riesen
2008-03-02 18:40 ` Carlos Rica
2008-03-02 21:38 ` Alex Riesen
2008-03-03 14:39 ` Carlos Rica
-- strict thread matches above, loose matches on Subject: below --
2008-03-04 22:11 Carlos Rica
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=1b46aba20803020454v322f061bi4f34a737e9e2b7f3@mail.gmail.com \
--to=jasampler@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=raa.lkml@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).