Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/lockfile-progs
Date: Wed, 19 Nov 2008 02:16:40 -0800 (PST)	[thread overview]
Message-ID: <20081119101640.F36C73C818@busybox.net> (raw)

Author: jacmet
Date: 2008-11-19 02:16:40 -0800 (Wed, 19 Nov 2008)
New Revision: 24098

Log:
lockfile-progs: fix patch-kernel invocation

Patch by Roberto A. Foglietta.

Closes #6364

Modified:
   trunk/buildroot/package/lockfile-progs/lockfile-progs.mk


Changeset:
Modified: trunk/buildroot/package/lockfile-progs/lockfile-progs.mk
===================================================================
--- trunk/buildroot/package/lockfile-progs/lockfile-progs.mk	2008-11-19 09:35:00 UTC (rev 24097)
+++ trunk/buildroot/package/lockfile-progs/lockfile-progs.mk	2008-11-19 10:16:40 UTC (rev 24098)
@@ -17,7 +17,7 @@
 
 $(LOCKFILE_PROGS_DIR)/.unpacked: $(DL_DIR)/$(LOCKFILE_PROGS_SOURCE)
 	$(LOCKFILE_PROGS_CAT) $(DL_DIR)/$(LOCKFILE_PROGS_SOURCE) | tar -C $(BUILD_DIR) $(TAR_OPTIONS) -
-	toolchain/patch-kernel.sh $(LOCKFILE_PROGS_DIR) package/lockfile-progs/ *.patch
+	toolchain/patch-kernel.sh $(LOCKFILE_PROGS_DIR) package/lockfile-progs/ \*.patch
 	touch $(LOCKFILE_PROGS_DIR)/.unpacked
 
 $(TARGET_DIR)/$(LOCKFILE_PROGS_BINARY): $(LOCKFILE_PROGS_DIR)/.unpacked

             reply	other threads:[~2008-11-19 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 10:16 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-22  6:49 [Buildroot] svn commit: trunk/buildroot/package/lockfile-progs jacmet at uclibc.org
2008-05-20 21:35 ulf at uclibc.org
2007-10-18 22:23 vanokuten at uclibc.org
2007-07-17  0:25 sjhill 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=20081119101640.F36C73C818@busybox.net \
    --to=jacmet@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