From: Frans Pop <elendil@planet.nl>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [GIT] kbuild - 2nd batch
Date: Fri, 25 Sep 2009 21:57:27 +0200 [thread overview]
Message-ID: <200909252157.29628.elendil@planet.nl> (raw)
In-Reply-To: <20090925190702.GA3275@merkur.ravnborg.org>
On Monday 21 September Sam Ravnborg wrote:
> First (delayed) batch of kbuild stuff.
[...]
> And I guess a bit more if I find time to crawl through my mailbox.
On Friday 25 September Sam Ravnborg wrote:
> Here comes the 2nd batch of kbuild updates.
Hello Sam,
It would be really great if you could take the time to go through your
inbox (assuming mails to l-kbuild also end up there).
You should find one patch from me in it (sent twice) that was intended
for .32, titled:
kbuild: fix the binrpm-pkg target to work with KBUILD_OUTPUT set
No doubt there are also patches from others that were missed by Andrew and
were thus not included in your first pull via that circuitous route.
TIA,
FJP
prev parent reply other threads:[~2009-09-25 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 19:07 [GIT] kbuild - 2nd batch Sam Ravnborg
2009-09-25 19:57 ` Frans Pop [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=200909252157.29628.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