From: Jeff King <peff@peff.net>
To: Christoph Buchner <bilderbuchi@phononoia.at>
Cc: Clemens Buchacher <drizzd@aon.at>, git@vger.kernel.org
Subject: Re: Bug: git ls-files and ignored directories
Date: Fri, 1 Jun 2012 05:37:57 -0400 [thread overview]
Message-ID: <20120601093757.GE32340@sigill.intra.peff.net> (raw)
In-Reply-To: <20120531101451.C35C5B4C00D@dd24126.kasserver.com>
On Thu, May 31, 2012 at 12:14:51PM +0200, Christoph Buchner wrote:
> This is the right place to report bugs, right?
Yes.
> Is there any protocol to follow I'm not aware of, to enable you to
> process this bug report?
Not really. You send the report, and you may or may not get a response
(just as you may or may not have somebody respond to you in a bug
tracker). Probably nobody has had a chance to look at it yet. If there
is a history to the bug (which there is in this case), it is sometimes
helpful to cc the previous participants to see if they are still
interested in it.
> > I think I've been bitten by a bug in git ls-files - committed
> > directories (and files therein) which are matched by a "dir/"
> > gitignore rule are not shown by "git ls-files --exclude-standard
> > -i", although they should be. Matched files are shown.
> >
> > I've found a very brief discussion on this mailing list from March
> > 2011 about this, including a repro procedure which still is valid
> > today, at http://marc.info/?l=git&m=129926031808376&w=4
> >
> > Is that a known/in progress bug? If yes, (when) can a fix be
> > expected? How can I work around this in the meantime?
No, I don't think anybody is working on it at the moment (at least I
do not see anything near the time of that old discussion, nor do I
recall it being discussed since).
+cc Clemens, in case he had any work-in-progress as a result that did
not end up getting published.
-Peff
next prev parent reply other threads:[~2012-06-01 9:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 10:22 Bug: git ls-files and ignored directories Christoph Buchner
2012-05-31 10:14 ` Christoph Buchner
2012-06-01 9:37 ` Jeff King [this message]
2012-06-01 15:30 ` Clemens Buchacher
2012-06-01 16:03 ` Junio C Hamano
2012-06-01 18:28 ` Junio C Hamano
2012-06-01 19:22 ` Junio C Hamano
2012-06-02 10:33 ` Nguyen Thai Ngoc Duy
2012-06-02 11:00 ` Christoph Buchner
2012-06-02 22:56 ` Junio C Hamano
2012-06-03 11:44 ` Christoph Buchner
2012-06-03 22:24 ` Junio C Hamano
2012-06-04 2:12 ` 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=20120601093757.GE32340@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=bilderbuchi@phononoia.at \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
/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).