From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git <git@vger.kernel.org>
Subject: Re: Behavior of 'git add \*.txt': bug or feature?
Date: Wed, 16 Sep 2009 13:30:15 -0700 [thread overview]
Message-ID: <7vbplazl7s.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <vpqljke7jv8.fsf@bauges.imag.fr> (Matthieu Moy's message of "Wed\, 16 Sep 2009 21\:46\:51 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> It this the intended behavior? If so, what's the rationale for this?
I strongly suspect that it comes from the fact that we have two
definitions and three implementations of pathspec-aware tree traversal.
One family is unaware of shell-glob wildcards (they only do leading
directory path match) while the other know both leading directory path and
shell-glob.
It is on the list of long-term items to fix, as the change required is
quite involved.
next prev parent reply other threads:[~2009-09-16 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 19:46 Behavior of 'git add \*.txt': bug or feature? Matthieu Moy
2009-09-16 20:30 ` Junio C Hamano [this message]
2009-09-16 21:26 ` Matthieu Moy
2009-09-17 14:25 ` Clemens Buchacher
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=7vbplazl7s.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.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).