From: Avery Pennarun <apenwarr@gmail.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>,
Nanako Shiraishi <nanako3@lavabit.com>,
Marc Fournier <marc.fournier@camptocamp.com>,
git@vger.kernel.org
Subject: Re: git-subtree: directory mismatch
Date: Wed, 25 Nov 2009 18:45:22 -0500 [thread overview]
Message-ID: <32541b130911251545x212cc55el9f8d4bc44eadd45b@mail.gmail.com> (raw)
In-Reply-To: <20091125234122.GA31422@atjola.homenet>
2009/11/25 Björn Steinbrink <B.Steinbrink@gmx.de>:
> On 2009.11.25 18:20:45 -0500, Avery Pennarun wrote:
>> I read the earlier thread and I still don't quite understand this
>> point. What makes it difficult?
>
> I guess it's -Xfoo vs. -X foo (note the space). Same deal with log
> -S<string>. "git log -S foo" would look for an empty string (I guess)
> being added/removed in some commit in foo's history, while "git log
> -Sfoo" looks for "foo" being added/remove in HEAD's history.
Oh. Ouch. Isn't it standard for options-that-take-string-parameters
to always *require* that parameter? This seems to be how getopt
works. Basically "-X foo" is the same as "-Xfoo" in that system.
If parse_options doesn't already do this, should I try to add it somehow?
Avery
next prev parent reply other threads:[~2009-11-25 23:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 19:53 git-subtree: directory mismatch Marc Fournier
2009-11-24 21:48 ` Avery Pennarun
2009-11-24 23:08 ` Nanako Shiraishi
2009-11-25 18:28 ` Avery Pennarun
2009-11-25 19:31 ` Junio C Hamano
2009-11-25 19:48 ` Avery Pennarun
2009-11-25 20:20 ` Junio C Hamano
2009-11-25 23:17 ` Johannes Schindelin
2009-11-25 23:20 ` Avery Pennarun
2009-11-25 23:41 ` Björn Steinbrink
2009-11-25 23:45 ` Avery Pennarun [this message]
2009-11-25 14:32 ` Marc Fournier
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=32541b130911251545x212cc55el9f8d4bc44eadd45b@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=B.Steinbrink@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marc.fournier@camptocamp.com \
--cc=nanako3@lavabit.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