From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain
Date: Sat, 29 Mar 2008 16:10:48 -0700 (PDT) [thread overview]
Message-ID: <20080329231048.1533A3C48B@busybox.net> (raw)
Author: ulf
Date: 2008-03-29 16:10:47 -0700 (Sat, 29 Mar 2008)
New Revision: 21568
Log:
Force use of bash for patching
Modified:
trunk/buildroot/toolchain/patch-kernel.sh
Changeset:
Modified: trunk/buildroot/toolchain/patch-kernel.sh
===================================================================
--- trunk/buildroot/toolchain/patch-kernel.sh 2008-03-29 23:09:46 UTC (rev 21567)
+++ trunk/buildroot/toolchain/patch-kernel.sh 2008-03-29 23:10:47 UTC (rev 21568)
@@ -1,4 +1,4 @@
-#! /bin/sh
+#! /bin/bash
# A little script I whipped up to make it easy to
# patch source trees and have sane error handling
# -Erik
next reply other threads:[~2008-03-29 23:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 23:10 ulf at uclibc.org [this message]
2008-03-30 13:03 ` [Buildroot] svn commit: trunk/buildroot/toolchain Peter Korsgaard
2008-03-30 23:39 ` Hamish Moffatt
2008-03-31 6:49 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-01-02 20:31 jacmet at uclibc.org
2008-12-23 10:21 jacmet at uclibc.org
2008-06-16 7:15 jacmet at uclibc.org
2008-03-29 11:04 ulf at uclibc.org
2008-03-13 17:10 ninevoltz at uclibc.org
2008-03-13 18:23 ` Peter Korsgaard
2008-03-13 18:28 ` John Voltz
2008-03-13 19:35 ` Peter Korsgaard
2008-03-13 20:39 ` John Voltz
2007-10-05 11:02 aldot at uclibc.org
2007-09-28 19:56 ulf at uclibc.org
2007-09-25 22:03 aldot at uclibc.org
2007-09-25 21:49 aldot at uclibc.org
2007-08-21 19:45 aldot at uclibc.org
2007-07-07 9:31 aldot at uclibc.org
2007-06-20 12:00 aldot at uclibc.org
2007-03-21 10:55 aldot at uclibc.org
2007-01-24 14:50 aldot at uclibc.org
2007-01-21 11:34 aldot at uclibc.org
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=20080329231048.1533A3C48B@busybox.net \
--to=ulf@uclibc.org \
--cc=buildroot@busybox.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