From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] kbuild fix for 2.6.33
Date: Tue, 5 Jan 2010 16:50:38 +0100 [thread overview]
Message-ID: <20100105155038.GA20834@sepie.suse.cz> (raw)
Hi Linus,
please pull this to fix build with /bin/sh -> dash (as used in Ubuntu).
Thanks!
Michal
The following changes since commit 45d28b097280a78893ce25a5d0db41e6a2717853:
Linus Torvalds (1):
Merge branch 'reiserfs/kill-bkl' of git://git.kernel.org/.../frederic/random-tracing
are available in the git repository at:
git://repo.or.cz/linux-kbuild.git for-33
Jonathan Nieder (1):
kbuild: really fix bzImage build with non-bash sh
scripts/Makefile.lib | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
next reply other threads:[~2010-01-05 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 15:50 Michal Marek [this message]
2010-01-09 22:48 ` [GIT PULL] kbuild fix for 2.6.33 Jonathan Nieder
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=20100105155038.GA20834@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=jrnieder@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).