From: Jeff King <peff@peff.net>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: SungHyun Nam <goweol@gmail.com>, git@vger.kernel.org
Subject: Re: 'git add' regression in git-1.7?
Date: Fri, 19 Feb 2010 00:34:31 -0500 [thread overview]
Message-ID: <20100219053431.GB22645@coredump.intra.peff.net> (raw)
In-Reply-To: <32541b131002182115t5501d0d1u19367a4d8e7627e4@mail.gmail.com>
On Fri, Feb 19, 2010 at 12:15:02AM -0500, Avery Pennarun wrote:
> On Fri, Feb 19, 2010 at 12:04 AM, SungHyun Nam <goweol@gmail.com> wrote:
> > Well, before sending the previous email, I checked the
> > RelNotes-1.7.*.txt, and could not find such a change by searching
> > 'git add'. So, I thought it's a regression.
>
> As far as I know, git add has refused to add ignored files for as long
> as I can remember. Maybe there was briefly a bug in this behaviour
> that was later fixed...
>
> If you use 'git bisect' on the git repo, you could probably discover
> what happened, in case you're interested.
It was intentional. Try 48ffef9 (ls-files: fix overeager pathspec
optimization, 2010-01-08).
-Peff
next prev parent reply other threads:[~2010-02-19 5:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 4:30 'git add' regression in git-1.7? SungHyun Nam
2010-02-19 4:42 ` Avery Pennarun
2010-02-19 5:04 ` SungHyun Nam
2010-02-19 5:15 ` Avery Pennarun
2010-02-19 5:34 ` Jeff King [this message]
2010-02-19 6:02 ` Jeff King
2010-02-19 8:24 ` Jeff King
2010-03-01 2:00 ` Junio C Hamano
2010-03-01 3:25 ` [PATCH] add: fail "git add ignored-dir/file" without -f Junio C Hamano
2010-03-01 8:26 ` [PATCH 1/3] t0050: mark non-working test as such Junio C Hamano
2010-03-09 22:37 ` 'git add' regression in git-1.7? Jeff King
2010-03-09 23:09 ` Jeff King
2010-03-10 7:06 ` Junio C Hamano
2010-03-11 7:15 ` Jeff King
2010-03-14 6:34 ` Junio C Hamano
2010-03-14 20:44 ` Jeff King
2010-03-15 2:02 ` Junio C Hamano
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=20100219053431.GB22645@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=goweol@gmail.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).