git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Marko Poutiainen <regs@sofistes.net>, git@vger.kernel.org
Subject: Re: Gitignore matching "git add" wildcard prevents operation
Date: Thu, 14 Jan 2010 15:39:28 -0500	[thread overview]
Message-ID: <20100114203928.GA26883@coredump.intra.peff.net> (raw)
In-Reply-To: <7vljg0bfox.fsf@alter.siamese.dyndns.org>

On Thu, Jan 14, 2010 at 12:21:34PM -0800, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> > ... But there is no way to
> > use the shell wildcard and get the behavior you want (not even a "git
> > add --really-ignore-my-ignores a.*").
> 
> Perhaps you want to run
> 
> 	$ git add 'a.*'
> 
> Notice that the wildcard is protected from the shell.

Ugh. You're right that it does work, but I don't expect users to make
the intuitive jump from the OP's problem to this solution (I certainly
didn't). In particular:

  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.

-Peff

  reply	other threads:[~2010-01-14 20:39 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 [this message]
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
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=20100114203928.GA26883@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 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).