From: Jeff King <peff@peff.net>
To: Lars Hoss <lars@woeye.net>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git status doesn't handle submodules properly on OSX
Date: Wed, 15 Oct 2008 08:49:43 -0400 [thread overview]
Message-ID: <20081015124943.GA10816@sigill.intra.peff.net> (raw)
In-Reply-To: <c60a85c1297be6446ad92a3e7723ddc8.squirrel@webmail.highteq.net>
On Wed, Oct 15, 2008 at 02:07:17PM +0200, Lars Hoss wrote:
> two days ago I posted about an issue:
> http://thread.gmane.org/gmane.comp.version-control.git/98171
>
> After more testing I can confirm it is indeed a bug.
>
> 1.6.0.2 on OSX Leopard doesn't work. After adding a submodule
> the folder of the submodule will always get listed under
> "Untracked files" when calling git status.
>
> 1.5.6, however, works fine. I have not tested trunk yet.
I wasn't able to reproduce your bug on my Linux box. Can you bisect to
find the faulty commit?
-Peff
next prev parent reply other threads:[~2008-10-15 12:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 12:07 [BUG] git status doesn't handle submodules properly on OSX Lars Hoss
2008-10-15 12:49 ` Jeff King [this message]
2008-10-15 14:30 ` Lars Hoss
2008-10-15 14:38 ` Pieter de Bie
2008-10-15 14:51 ` Lars Hoss
2008-10-15 14:59 ` Pieter de Bie
2008-10-15 15:14 ` Lars Hoss
2008-10-15 15:01 ` Richard Bubel
2008-10-15 15:21 ` Lars Hoss
2008-10-16 9:49 ` Pedro Melo
2008-10-16 9:48 ` Pedro Melo
2008-10-16 10:30 ` Lars Hoss
2008-10-16 11:23 ` Lars Hoss
2008-10-16 11:39 ` Johannes Sixt
2008-10-16 11:53 ` Lars Hoss
2008-10-16 12:30 ` Lars Hoss
2008-10-16 14:18 ` Jeff King
2008-10-16 14:59 ` [PATCH] refactor handling of "other" files in ls-files and status Jeff King
2008-10-16 15:07 ` Jeff King
2008-10-17 23:58 ` Junio C Hamano
2008-10-16 9:43 ` [BUG] git status doesn't handle submodules properly on OSX Pedro Melo
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=20081015124943.GA10816@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=lars@woeye.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).