From: Frans Pop <elendil@planet.nl>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: torvalds@linux-foundation.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PULL] kbuild fixes
Date: Wed, 29 Oct 2008 23:56:15 +0100 [thread overview]
Message-ID: <200810292356.16804.elendil@planet.nl> (raw)
In-Reply-To: <20081029215137.GA25023@uranus.ravnborg.org>
Sam Ravnborg wrote:
> I expect at least one more pull as I have not been through
> all patches yet - and need to visit bugzilla too.
Hi Sam,
Is the patch [1] I pointed out to you in [2] on your ToDo list for that?
I'm asking as there was no reply to that mail yet.
I now see that in the archive my message had a "parse failure" for some
reason. Maybe that explains...
Cheers,
FJP
[1] http://lkml.org/lkml/2008/9/13/102
[2] http://lkml.org/lkml/2008/10/25/232
next prev parent reply other threads:[~2008-10-29 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 21:51 [PULL] kbuild fixes Sam Ravnborg
2008-10-29 22:56 ` Frans Pop [this message]
2008-10-30 5:39 ` Sam Ravnborg
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=200810292356.16804.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
/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