git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Git List <git@vger.kernel.org>,
	Ian Clatworthy <ian.clatworthy@canonical.com>,
	Matt McClure <mlm@aya.yale.edu>,
	Miklos Vajna <vmiklos@frugalware.org>,
	Julian Phillips <julian@quantumfyre.co.uk>,
	vcs-fast-import-devs@lists.launchpad.net
Subject: Re: [PATCH v6 5/6] fast-import: add option command
Date: Thu, 3 Sep 2009 06:55:38 +0200	[thread overview]
Message-ID: <fabb9a1e0909022155r254c41c6s9ed962313c241e9@mail.gmail.com> (raw)
In-Reply-To: <7vskf4px6j.fsf@alter.siamese.dyndns.org>

Heya,

On Thu, Sep 3, 2009 at 04:41, Junio C Hamano<gitster@pobox.com> wrote:
> If "option git something-unknown" is given, it is clear that the tool that
> generated the stream assumed that such an option exists in the importer;
> it might appear prudent to abort the operation.
>
> But what about "option hg something"?

I think we should assume that if we see 'option not-us foo' without a
preceeding 'feature not-us-option', the frontend does not require us
to understand the option (perhaps because they also specify 'option
git foo'.

> If that is the sensible thing to do, then we obviously should ignore
> "option hg anything", but at the same time we should ignore "option git
> we-do-not-know-what-it-does".

Perhaps, frontends could then use 'feature git-quiet-option' if it
wants to make sure it is supported.

> I think at least the function should be made conditional to die() if it
> was called from parse_argv() but simply ignore unknown if it was called
> from the input stream.

Makes sense, what do the fast-import devs think?

>> +static void parse_option(void)
>> +{
>> +     char* option = command_buf.buf + 11;
>
> ERROR: "foo* bar" should be "foo *bar"

Ah, I thought I had fixed all of those, apologies.

> ERROR: do not use C99 // comments
> ERROR: do not use C99 // comments

Will fix in the next version (after we decide on what to do with
unknown git options).

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2009-09-03  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 17:56 [PATCH v6 0/6] fast-import: add new feature and mark command Sverre Rabbelier
2009-09-02 17:56 ` [PATCH v6 1/6] fast-import: put option parsing code in separate functions Sverre Rabbelier
2009-09-02 17:56   ` [PATCH v6 2/6] fast-import: put marks reading in it's own function Sverre Rabbelier
2009-09-02 17:57     ` [PATCH v6 3/6] fast-import: add feature command Sverre Rabbelier
2009-09-02 17:57       ` [PATCH v6 4/6] fast-import: test the new " Sverre Rabbelier
2009-09-02 17:57         ` [PATCH v6 5/6] fast-import: add option command Sverre Rabbelier
2009-09-02 17:57           ` [PATCH v6 6/6] fast-import: test the new " Sverre Rabbelier
2009-09-03  2:41           ` [PATCH v6 5/6] fast-import: add " Junio C Hamano
2009-09-03  4:55             ` Sverre Rabbelier [this message]
2009-09-04  3:42               ` Ian Clatworthy

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=fabb9a1e0909022155r254c41c6s9ed962313c241e9@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ian.clatworthy@canonical.com \
    --cc=julian@quantumfyre.co.uk \
    --cc=mlm@aya.yale.edu \
    --cc=spearce@spearce.org \
    --cc=vcs-fast-import-devs@lists.launchpad.net \
    --cc=vmiklos@frugalware.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).