From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org, "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 2/2] pull: document usage via OPTIONS_SPEC
Date: Fri, 22 Feb 2008 20:40:15 -0500 [thread overview]
Message-ID: <76718490802221740ldbf077ch80aa6ec3fedbba61@mail.gmail.com> (raw)
In-Reply-To: <7vk5kw5v79.fsf@gitster.siamese.dyndns.org>
On Fri, Feb 22, 2008 at 8:15 PM, Junio C Hamano <gitster@pobox.com> wrote:
> OPTIONS_SPEC is not just for documentation but it actively mucks
> with the incoming options list.
>
> Have you checked if you did not break the actual parsing?
Duh, no. Sorry. Will do.
j.
next prev parent reply other threads:[~2008-02-23 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 0:52 [PATCH 1/2] pull: pass --strategy along to to rebase Jay Soffian
2008-02-23 0:52 ` [PATCH 2/2] pull: document usage via OPTIONS_SPEC Jay Soffian
2008-02-23 1:15 ` Junio C Hamano
2008-02-23 1:40 ` Jay Soffian [this message]
2008-02-26 20:42 ` [PATCH v2] " Jay Soffian
2008-02-26 21:23 ` Junio C Hamano
2008-02-26 21:37 ` Jay Soffian
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=76718490802221740ldbf077ch80aa6ec3fedbba61@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).