From: "Lars Hoss" <lars@woeye.net>
To: "Pedro Melo" <melo@simplicidade.org>
Cc: "Lars Hoss" <lars@woeye.net>, "Pieter de Bie" <pdebie@ai.rug.nl>,
"Jeff King" <peff@peff.net>,
"Git Mailinglist" <git@vger.kernel.org>
Subject: Re: [BUG] git status doesn't handle submodules properly on OSX
Date: Thu, 16 Oct 2008 12:30:19 +0200 (CEST) [thread overview]
Message-ID: <fa8b32c2ff1d10914c5f3f24f79db91b.squirrel@webmail.highteq.net> (raw)
In-Reply-To: <524C98C8-C3A5-4501-932A-2F0ACDE2886A@simplicidade.org>
Hi!
I've cloned git this morning in order to try a build from this.
But chances are small that it will make a difference. Because from
the portfile I can see that macports just downloads 1.6.0.2 release
and builds it without any special patches or configure options.
As I said before, 1.5.6 works fine for me. But why 1.6.0.2 does not
work on my box - I don't know yet. Since Pedro uses a case-insensitive
volume as well, the problem seems not be related to sensitve/insensitive.
Now that I have a git clone on my box I might try bisect as well.
Yours,
Lars
> On Oct 15, 2008, at 3:51 PM, Lars Hoss wrote:
>
>>> Works for me on Leopard
>>>
>>> Vienna:a pieter$ git submodule add ~/projects/GitX/ gitx
>>> Initialized empty Git repository in /Users/pieter/a/gitx/.git/
>>> Vienna:a pieter$ git st
>>> # On branch master
>>> # Changes to be committed:
>>> # (use "git reset HEAD <file>..." to unstage)
>>> #
>>> # new file: .gitmodules
>>> # new file: gitx
>>> #
>>> Vienna:a pieter$ git --version
>>> git version 1.6.0.2.415.gf9137
>>
>> My git version "1.6.0.2" says:
>>
>> # On branch master
>> # Changes to be committed:
>> # (use "git reset HEAD <file>..." to unstage)
>> #
>> # new file: .gitmodules
>> # new file: lib
>> #
>> # Untracked files:
>> # (use "git add <file>..." to include in what will be committed)
>> #
>> # lib/
>> git --version
>> git version 1.6.0.2
>>
>> Git was build from macports.
>
> hmms.. Really, I know about fink and Macports and all others, but I'm
> using Mac OS X since version 10.1 (when compiling OSS software was
> near impossible due to Apple decisions) and I've always had better
> results with compiling my own than using any of those OSS repositories.
>
> I understand the appeal, it seems easier, but I would recommend that
> you compile yourself the software packages you depend on.
>
> Regarding git, I saw a git-build.sh script floating around. If you
> cannot find it, you might want to try my own recipe
> (http://tinyurl.com/4ayze6
> ). I compile git master every day (cron) and thats the one I use on my
> main machine.
>
> Best regards,
> --
> Pedro Melo
> Blog: http://www.simplicidade.org/notes/
> XMPP ID: melo@simplicidade.org
> Use XMPP!
>
>
>
next prev parent reply other threads:[~2008-10-16 10:28 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
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 [this message]
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=fa8b32c2ff1d10914c5f3f24f79db91b.squirrel@webmail.highteq.net \
--to=lars@woeye.net \
--cc=git@vger.kernel.org \
--cc=melo@simplicidade.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).