From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Wincent Colaiuta <win@wincent.com>, git@vger.kernel.org
Subject: Re: "git add -i" with path gives "Argument list too long"
Date: Sun, 21 Mar 2010 21:41:00 -0400 [thread overview]
Message-ID: <20100322014100.GA7717@coredump.intra.peff.net> (raw)
In-Reply-To: <7vwrx56tet.fsf@alter.siamese.dyndns.org>
On Sun, Mar 21, 2010 at 06:23:38PM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > their behavior. Junio could probably say more, or you will have to read
> > the code.
>
> Or read what I already said here a few times ;-) I generally do not want
> to repeat myself.
Well, yeah. :) What I meant was:
> There are two semantics of pathspecs:
>
> (1) exact match, or leading path. e.g.
>
> git ls-files Makefile Documentation/
>
> (2) exact match, leading path, or fnmatch(3).
>
> git ls-files Makefile Documentation/ '*.txt'
Is type (2) exactly fnmatch? Or are there subtle corner cases that
should be tested? For the implementation it shouldn't matter, as
hopefully the same code paths will be used, and "just like ls-files"
should be specification enough. But for testing, it might be nice to
enumerate some of the more subtle cases.
-Peff
next prev parent reply other threads:[~2010-03-22 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 20:52 "git add -i" with path gives "Argument list too long" Wincent Colaiuta
2010-03-22 0:39 ` Jeff King
2010-03-22 1:23 ` Junio C Hamano
2010-03-22 1:41 ` Jeff King [this message]
2010-03-22 1:55 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2010-01-04 18:43 Wincent Colaiuta
2010-01-05 4:14 ` Jeff King
2010-01-05 5:31 ` Junio C Hamano
2010-01-05 12:34 ` Wincent Colaiuta
2010-01-06 12:19 ` Jeff King
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=20100322014100.GA7717@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=win@wincent.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).