From: Sverre Rabbelier <srabbelier@gmail.com>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
"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>
Subject: Re: [PATCH v5 5/6] fast-import: add option command
Date: Thu, 27 Aug 2009 12:40:38 -0700 [thread overview]
Message-ID: <fabb9a1e0908271240la7cefd9k8476c0ab5ffd69d8@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0908271942090.6501@reaper.quantumfyre.co.uk>
Heya,
On Thu, Aug 27, 2009 at 11:44, Julian Phillips<julian@quantumfyre.co.uk> wrote:
> On Thu, 27 Aug 2009, Sverre Rabbelier wrote:
>> +Option commands must be the first commands on the input, to give an
>> +option command after any non-option command is an error.
>
> Er ... shouldn't that be the first thing _after_ the "feature git-options"
> command?
Correct, updated the code but not the docs. Fixed.
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2009-08-27 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 18:12 [PATCH v5 1/6] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-27 18:12 ` [PATCH v5 2/6] fast-import: put marks reading in it's own function Sverre Rabbelier
2009-08-27 18:12 ` [RFC PATCH v5 3/6] fast-import: add feature command Sverre Rabbelier
2009-08-27 18:12 ` [PATCH v5 4/6] fast-import: test the new " Sverre Rabbelier
2009-08-27 18:12 ` [PATCH v5 5/6] fast-import: add option command Sverre Rabbelier
2009-08-27 18:12 ` [PATCH v5 6/6] fast-import: test the new " Sverre Rabbelier
2009-08-27 18:46 ` Julian Phillips
2009-08-27 19:44 ` Sverre Rabbelier
2009-08-27 18:44 ` [PATCH v5 5/6] fast-import: add " Julian Phillips
2009-08-27 19:40 ` Sverre Rabbelier [this message]
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=fabb9a1e0908271240la7cefd9k8476c0ab5ffd69d8@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=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).