From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git List <git@vger.kernel.org>
Subject: Re: [RFC PATCH 0/3] fast-import: add option command
Date: Sun, 2 Aug 2009 17:15:22 -0700 [thread overview]
Message-ID: <20090803001522.GE1033@spearce.org> (raw)
In-Reply-To: <1249189570-26576-1-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.
...
> fast-import.c | 137 ++++++++++++++++++++++++++++++++++++-----------
> t/t9300-fast-import.sh | 33 ++++++++++++
> 2 files changed, 138 insertions(+), 32 deletions(-)
Some comments:
Since you are changing the language format, please also update the
documentation of the language.
It might be cleaner to say "option foo=value\n" because then the
if block to parse the command line and the if block to parse the
input stream are the same. When parsing argv just skip the "--"
and pass the rest of the argv value into the function, when parsing
the stream, just skip the "option " and pass the rest of the line
into the function.
This has come up before on the list. We had somewhat decided against
setting options in the stream header. The only option class that
really impacts the data itself is the date format, all others
are about local file paths or how noisy the command should be.
Thus we decided that the frontend should invoke `git fast-import`
itself if it cared about these options, and that's what any typical
frontend does.
--
Shawn.
next prev parent reply other threads:[~2009-08-03 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 1:29 option directive to fast-import Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 0/3] fast-import: add option command Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 1/2] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 2/2] fast-import: add option command Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 3/3] fast-import: test the new " Sverre Rabbelier
2009-08-02 7:09 ` [RFC PATCH v1a 1/3] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-03 0:15 ` Shawn O. Pearce [this message]
2009-08-03 4:31 ` [RFC PATCH 0/3] fast-import: add option command Sverre Rabbelier
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=20090803001522.GE1033@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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).