From: Ken Sharp <ken.sharp@ni.com>
To: openembedded-core@lists.openembedded.org
Cc: Ken Sharp <ken.sharp@ni.com>
Subject: [PATCH 1/2] udev-cache: Remove unnecessary tar read from stdin
Date: Tue, 21 Apr 2015 10:35:44 -0500 [thread overview]
Message-ID: <1429630545-17151-1-git-send-email-ken.sharp@ni.com> (raw)
xargs already formats the inputs to tar correctly, so the
'-T -' argument to tar is unnecessary.
Signed-off-by: Ken Sharp <ken.sharp@ni.com>
---
meta/recipes-core/udev/udev/udev-cache | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/udev/udev/udev-cache b/meta/recipes-core/udev/udev/udev-cache
index df97000..12f68fb 100644
--- a/meta/recipes-core/udev/udev/udev-cache
+++ b/meta/recipes-core/udev/udev/udev-cache
@@ -57,7 +57,7 @@ echo "Populating dev cache"
udevadm control --stop-exec-queue
sysconf_cmd > "$SYSCONF_TMP"
find /dev -xdev \( -type b -o -type c -o -type l \) | cut -c 2- \
- | xargs tar cf "${DEVCACHE_TMP}" -T-
+ | xargs tar cf "${DEVCACHE_TMP}"
gzip < "${DEVCACHE_TMP}" > "$DEVCACHE"
rm -f "${DEVCACHE_TMP}"
mv "$SYSCONF_TMP" "$SYSCONF_CACHED"
--
1.9.1
next reply other threads:[~2015-04-21 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 15:35 Ken Sharp [this message]
2015-04-21 15:35 ` [PATCH 2/2] udev-cache: improve error handling Ken Sharp
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=1429630545-17151-1-git-send-email-ken.sharp@ni.com \
--to=ken.sharp@ni.com \
--cc=openembedded-core@lists.openembedded.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