All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Git List <git@vger.kernel.org>
Subject: Re: [PATCH 3/4] fast-import: add option command
Date: Thu, 13 Aug 2009 07:45:39 -0700	[thread overview]
Message-ID: <20090813144539.GL1033@spearce.org> (raw)
In-Reply-To: <1250140186-12363-4-git-send-email-srabbelier@gmail.com>

Sverre Rabbelier <srabbelier@gmail.com> wrote:
> This allows the frontend to specify any of the supported options as
> long as no non-option command has been given. This way the
> user does not have to include any frontend-specific options, but
> instead she can rely on the frontend to tell fast-import what it
> needs.
> ---

Missing Signed-off-by.
 
> @@ -2460,6 +2465,16 @@ static void parse_one_option(const char *option)
>      }
>  }
>  
> +static void parse_option(void)
> +{
> +    char* option = command_buf.buf + 7;

Git style is "char *option", isn't it?

> +
> +	if (seen_non_option_command)
> +		die("Got option command '%s' after non-option command", option);

Indentation is messed up here.  1 tab per level, please.

-- 
Shawn.

  parent reply	other threads:[~2009-08-13 14:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  5:09 [PATCH 0/4] fast-import: add a new option command Sverre Rabbelier
2009-08-13  5:09 ` [PATCH 1/4] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-13  5:09   ` [PATCH 2/4] fast-import: define a new option command Sverre Rabbelier
2009-08-13  5:09     ` [PATCH 3/4] fast-import: add " Sverre Rabbelier
2009-08-13  5:09       ` [PATCH 4/4] fast-import: test the new " Sverre Rabbelier
2009-08-13 14:45       ` Shawn O. Pearce [this message]
2009-08-13 14:43     ` [PATCH 2/4] fast-import: define a " Shawn O. Pearce
2009-08-13 14:56       ` Johannes Schindelin
2009-08-13 15:04         ` Shawn O. Pearce
     [not found]           ` <fabb9a1e0908130812s297ccfc6vd6b746daf1dcc69a@mail.gmail.com>
2009-08-13 15:24             ` Shawn O. Pearce
2009-08-13 16:26               ` Sverre Rabbelier
2009-08-13 17:07                 ` Johannes Schindelin
2009-08-13 17:09                   ` Sverre Rabbelier
2009-08-13 17:25                     ` Shawn O. Pearce
2009-08-13 17:28                       ` Sverre Rabbelier
2009-08-13 17:41                         ` Shawn O. Pearce
2009-08-13 17:44                           ` Sverre Rabbelier
2009-08-13 17:52                             ` Shawn O. Pearce
2009-08-13 21:51                               ` Johannes Schindelin
2009-08-13 22:01                                 ` Sverre Rabbelier
2009-08-13 22:12                                   ` Shawn O. Pearce
2009-08-13 22:17                                     ` Sverre Rabbelier
2009-08-13 19:26                       ` Junio C Hamano
2009-08-13 20:01                         ` Sverre Rabbelier
2009-08-13 20:42                           ` Junio C Hamano
2009-08-13 21:14                             ` Sverre Rabbelier
2009-11-23 17:39                       ` Sverre Rabbelier
2009-11-23 20:50                         ` Shawn O. Pearce
2009-08-13 10:19   ` [PATCH 1/4] fast-import: put option parsing code in seperate functions Johannes Schindelin
2009-08-13 14:40     ` Shawn O. Pearce

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=20090813144539.GL1033@spearce.org \
    --to=spearce@spearce.org \
    --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 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.