From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Marko Poutiainen <regs@sofistes.net>,
git@vger.kernel.org, Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Gitignore matching "git add" wildcard prevents operation
Date: Fri, 15 Jan 2010 16:34:19 +0100 [thread overview]
Message-ID: <20100115153419.GA12982@vidovic> (raw)
In-Reply-To: <20100114203928.GA26883@coredump.intra.peff.net>
The 14/01/10, Jeff King wrote:
> 1. Most programs don't take their own globs. Without knowing that git
> can do so, there is no reason to discover it in this instance. I
> can see searching the manpage for options, but not for a discussion
> of globbing behavior.
>
> 2. They would have to know that using a git-glob will magically change
> the error-checking behavior.
Not sure. This isn't a Git-particular issue.
Users may hit this with a lot of other unix tools (sed, grep, find,
etc). So, we can expect either
they already know the issue;
or
they are discovering it using Git.
Most of the tools I talk about do have a manual section about globbing.
Users could learn globs with Git too and expect the same behaviour
somewhere else.
--
Nicolas Sebrecht
next prev parent reply other threads:[~2010-01-15 15:34 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 [this message]
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
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=20100115153419.GA12982@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.