From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: sam@ravnborg.org, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: Latest git-x86 doesn't build on 32bit
Date: Tue, 15 Jan 2008 11:01:30 +0100 [thread overview]
Message-ID: <20080115100130.GA27029@elte.hu> (raw)
In-Reply-To: <20080115090829.GB29301@one.firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> On Tue, Jan 15, 2008 at 09:57:57AM +0100, Ingo Molnar wrote:
> >
> > * Andi Kleen <andi@firstfloor.org> wrote:
> >
> > > On a fresh object dir I get for a 32bit build:
> >
> > you seem to have a modified git repository.
>
> Would surprise me -- i regularly remove the old one and reclone fresh.
>
> Also didn't other people complain about build problems too?
not that i know of. (Got reports about the "only half of x86.git got
uploaded last night" problem but that is distinct.)
> Anyways I'll try today's git now.
ok.
Ingo
prev parent reply other threads:[~2008-01-15 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 22:16 Latest git-x86 doesn't build on 32bit Andi Kleen
2008-01-15 8:29 ` Ingo Molnar
2008-01-15 8:57 ` Ingo Molnar
2008-01-15 9:08 ` Andi Kleen
2008-01-15 10:01 ` Ingo Molnar [this message]
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=20080115100130.GA27029@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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