From: "Lars Hoss" <lars@woeye.net>
To: "Pieter de Bie" <pdebie@ai.rug.nl>
Cc: "Lars Hoss" <lars@woeye.net>, "Jeff King" <peff@peff.net>,
"Git Mailinglist" <git@vger.kernel.org>
Subject: Re: [BUG] git status doesn't handle submodules properly on OSX
Date: Wed, 15 Oct 2008 17:14:21 +0200 (CEST) [thread overview]
Message-ID: <cb12ad6f061a80750569e3f8b9d9b9d0.squirrel@webmail.highteq.net> (raw)
In-Reply-To: <A0A3837E-7F85-4172-A8BA-969BFD46CF48@ai.rug.nl>
> I just tested 1.6.0.2, and had no problems. Perhaps macports is doing
> something odd?
Actually this was my idea first. Thus I build git from the sources the
portfile links to myself. The bug, however, remains.
The link is: http://www.kernel.org/pub/software/scm/git/git-1.6.0.2.tar.bz2.
I've tested this on two machines, both using latest version of Leopard.
And there was another poster on this forum who had the very same issue.
Now the interesting question is what is different between Pieter's system
and mine? And why does 1.5.6 work fine?
As soon as I am at home I will try bisect. I am currently at work behind a
big bad firewall ;)
Yours,
Lars
next prev parent reply other threads:[~2008-10-15 15:12 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
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 [this message]
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=cb12ad6f061a80750569e3f8b9d9b9d0.squirrel@webmail.highteq.net \
--to=lars@woeye.net \
--cc=git@vger.kernel.org \
--cc=pdebie@ai.rug.nl \
--cc=peff@peff.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).