From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/bash
Date: Wed, 22 Aug 2007 02:29:50 -0700 (PDT) [thread overview]
Message-ID: <20070822092950.5BEE8A65AD@busybox.net> (raw)
Author: ulf
Date: 2007-08-22 02:29:49 -0700 (Wed, 22 Aug 2007)
New Revision: 19636
Log:
Fix bad patch naming scheme
Modified:
trunk/buildroot/package/bash/bash.mk
Changeset:
Modified: trunk/buildroot/package/bash/bash.mk
===================================================================
--- trunk/buildroot/package/bash/bash.mk 2007-08-22 09:22:32 UTC (rev 19635)
+++ trunk/buildroot/package/bash/bash.mk 2007-08-22 09:29:49 UTC (rev 19636)
@@ -19,7 +19,7 @@
bash-unpacked: $(BASH_DIR)/.unpacked
$(BASH_DIR)/.unpacked: $(DL_DIR)/$(BASH_SOURCE)
$(BASH_CAT) $(DL_DIR)/$(BASH_SOURCE) | tar -C $(BUILD_DIR) $(TAR_OPTIONS) -
- toolchain/patch-kernel.sh $(BASH_DIR) package/bash/ bash??-*
+ toolchain/patch-kernel.sh $(BASH_DIR) package/bash/ bash??-\*
# This is broken when -lintl is added to LIBS
$(SED) 's,LIBS_FOR_BUILD =.*,LIBS_FOR_BUILD =,g' \
$(BASH_DIR)/builtins/Makefile.in
next reply other threads:[~2007-08-22 9:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 9:29 ulf at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 19:09 [Buildroot] svn commit: trunk/buildroot/package/bash wberrier at uclibc.org
2008-05-01 19:07 nkukard at uclibc.org
2008-04-29 20:03 nkukard at uclibc.org
2008-03-11 18:12 ninevoltz at uclibc.org
2007-10-07 18:23 aldot at uclibc.org
2007-08-22 9:41 ulf at uclibc.org
2007-08-11 23:57 ulf at uclibc.org
2007-07-11 13:55 ulf at uclibc.org
2007-06-25 11:22 aldot at uclibc.org
2007-06-25 11:17 aldot at uclibc.org
2007-04-06 11:55 aldot at uclibc.org
2007-02-16 13:11 aldot at uclibc.org
2006-12-08 12:50 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=20070822092950.5BEE8A65AD@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