From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Jeff King <peff@peff.net>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
Junio C Hamano <gitster@pobox.com>,
Marko Poutiainen <regs@sofistes.net>,
git@vger.kernel.org
Subject: Re: Gitignore matching "git add" wildcard prevents operation
Date: Fri, 15 Jan 2010 19:06:12 +0100 [thread overview]
Message-ID: <20100115180612.GD12982@vidovic> (raw)
In-Reply-To: <20100115163021.GA1947@coredump.intra.peff.net>
The 15/01/10, Jeff King wrote:
> On Fri, Jan 15, 2010 at 05:11:07PM +0100, Nicolas Sebrecht wrote:
>
> > > I don't understand what you mean. How does "sed" do its own globbing of
> > > the command line?
> >
> > Well, we are in the same dilemma as the other tools. The internal
> > globbing rules are explained in the related man page.
>
> Maybe I wasn't clear: to my knowledge, "sed" does not do any globbing
> itself.
"sed" does /pattern matching/ which is the meaning I give to /globbing/.
Sure, "sed" doesn't do /shell globbing/ but is fed from it. We obviously
agree here. :-)
> But that is not my complaint; my complaint was mainly that
> git's solution to this is not easily discoverable by an uninformed user.
I agree in that it is not easily discoverable. But I don't think Git's
solution is worse than any other tool. The "discoverabiliy" looks equal
to any other tool for me. As you said, to do a good job we should be
able to know what was the original command-line, which isn't possible.
--
Nicolas Sebrecht
next prev parent reply other threads:[~2010-01-15 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 18:18 Gitignore matching "git add" wildcard prevents operation Marko Poutiainen
2010-01-14 19:52 ` Jeff King
2010-01-14 20:21 ` Junio C Hamano
2010-01-14 20:39 ` Jeff King
2010-01-15 15:34 ` Nicolas Sebrecht
2010-01-15 15:48 ` Jeff King
2010-01-15 16:11 ` Nicolas Sebrecht
2010-01-15 16:30 ` Jeff King
2010-01-15 18:06 ` Nicolas Sebrecht [this message]
2010-01-15 18:17 ` Junio C Hamano
2010-01-14 21:07 ` Marko Poutiainen
2010-01-15 15:39 ` Nicolas Sebrecht
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=20100115180612.GD12982@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=regs@sofistes.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.