From: Michael Ellerman <michaele@au1.ibm.com>
To: Wolfgang Pfeiffer <roto@gmx.net>
Cc: linux-ppc <linuxppc-dev@ozlabs.org>,
Michael Ellerman <ellerman@au1.ibm.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: latest git: compile error: arch/powerpc/kernel/built-in.o
Date: Fri, 18 Aug 2006 10:01:42 +1000 [thread overview]
Message-ID: <1155859302.20832.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20060817120653.GA3440@localhost>
On Thu, 2006-08-17 at 14:06 +0200, Wolfgang Pfeiffer wrote:
> On Thu, Aug 17, 2006 at 04:41:58PM +1000, Paul Mackerras wrote:
> > Wolfgang Pfeiffer writes:
> >
> > > Strange tho' - for me at least - that these patches from about 5 weeks (!)
> > > ago still don't seem to have made it into the current git tree ...
> >
> > 5 weeks ago was a particularly bad time for patches trying to get into
> > the git tree, since I was on vacation and then travelling to OLS. :)
>
> [ ... ]
>
> Michael, Paul, and everyone else being involved:
>
> My apologies for my perhaps too strong wording when I was complaining
> about the delay ... I didn't mean the words as ugly as they actually
> might read ...
No worries, thanks for catching the error and reporting it.
cheers
--
Michael Ellerman
IBM OzLabs
email: michaele@au.ibm.com
stime: ellerman@au1.ibm.com
notes: Michael Ellerman/Australia/IBM
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
next prev parent reply other threads:[~2006-08-18 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 18:11 latest git: compile error: arch/powerpc/kernel/built-in.o Wolfgang Pfeiffer
2006-08-10 21:14 ` Haren Myneni
2006-08-10 23:21 ` Wolfgang Pfeiffer
2006-08-10 23:48 ` Michael Ellerman
2006-08-17 6:41 ` Paul Mackerras
2006-08-17 12:06 ` Wolfgang Pfeiffer
2006-08-18 0:01 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 6:13 Niels Kristian Bech Jensen
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=1155859302.20832.0.camel@localhost.localdomain \
--to=michaele@au1.ibm.com \
--cc=ellerman@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=roto@gmx.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).