From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
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 18:55:47 -0700 [thread overview]
Message-ID: <7veijd3ysc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100322014100.GA7717@coredump.intra.peff.net> (Jeff King's message of "Sun\, 21 Mar 2010 21\:41\:00 -0400")
Jeff King <peff@peff.net> writes:
> Is type (2) exactly fnmatch?
It calls fnmatch(3) but without FNM_PATHNAME nor FNM_PERIOD, which makes
me sometimes wonder if it was a historical mistake and go to "git log" to
check, but it is more-or-less deliberate choice, as illustrated by the
'arch/i386/*.[ch]' example in 5be4efb ([PATCH] Make "git-ls-files" work in
subdirectories, 2005-08-21).
next prev parent reply other threads:[~2010-03-22 1:56 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
2010-03-22 1:55 ` Junio C Hamano [this message]
-- 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=7veijd3ysc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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).