From: Jeff King <peff@peff.net>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Explicitly adding ignored files in subdirectories not working
Date: Tue, 23 Feb 2010 23:59:58 -0500 [thread overview]
Message-ID: <20100224045958.GA2385@coredump.intra.peff.net> (raw)
In-Reply-To: <fabb9a1e1002231307o2c3499e6k3f1026f71a544b16@mail.gmail.com>
On Tue, Feb 23, 2010 at 10:07:52PM +0100, Sverre Rabbelier wrote:
> I've been bitten by this before, is this behavior intentional? We
> don't even warn that the user's action was ignored; at the very least
> we should do that. The current behavior is just frustrating.
It is intentional to consider them ignored (but was broken prior to
v1.7.0), but it is a bug not to complain to the user. See:
http://thread.gmane.org/gmane.comp.version-control.git/140405
-Peff
next prev parent reply other threads:[~2010-02-24 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 21:07 Explicitly adding ignored files in subdirectories not working Sverre Rabbelier
2010-02-23 21:50 ` Johannes Schindelin
2010-02-23 21:58 ` Sverre Rabbelier
2010-02-23 22:11 ` Johannes Schindelin
2010-02-24 4:59 ` Jeff King [this message]
2010-02-27 12:59 ` Sverre Rabbelier
2010-02-27 16:58 ` Junio C Hamano
2010-02-27 17:03 ` Sverre Rabbelier
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=20100224045958.GA2385@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=srabbelier@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).