From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: /
Date: Sun, 10 Apr 2022 11:37:42 +0000 (UTC) [thread overview]
Message-ID: <1649590640.26c57df5469813c897b8c7d34a969a3dc483e019.sam@gentoo> (raw)
commit: 26c57df5469813c897b8c7d34a969a3dc483e019
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 10 11:37:20 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 10 11:37:20 2022 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=26c57df5
make-tarball.sh: just use -a to tar
This is what I'd really meant to do the other day for .xz;
let tar autodetect based on extension.
Signed-off-by: Sam James <sam <AT> gentoo.org>
make-tarball.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/make-tarball.sh b/make-tarball.sh
index 94035e3..1d08c02 100755
--- a/make-tarball.sh
+++ b/make-tarball.sh
@@ -113,23 +113,23 @@ find tmp/ -name CVS -type d | xargs rm -rf
# standard jobbies
[[ -n ${PATCH_VER} ]] && {
-tar -Jcf gcc-${sgver}-patches-${PATCH_VER}.tar.xz \
+tar -acf gcc-${sgver}-patches-${PATCH_VER}.tar.xz \
-C tmp patch || exit 1 ; }
[[ -n ${MUSL_VER} ]] && {
-tar -Jcf gcc-${sgver}-musl-patches-${MUSL_VER}.tar.xz \
+tar -acf gcc-${sgver}-musl-patches-${MUSL_VER}.tar.xz \
-C tmp musl || exit 1 ; }
[[ -n ${PIE_VER} ]] && {
-tar -Jcf gcc-${sgver}-piepatches-v${PIE_VER}.tar.xz \
+tar -acf gcc-${sgver}-piepatches-v${PIE_VER}.tar.xz \
-C tmp piepatch || exit 1 ; }
[[ -n ${SPECS_VER} ]] && {
-tar -Jcf gcc-${sgver}-specs-${SPECS_VER}.tar.xz \
+tar -acf gcc-${sgver}-specs-${SPECS_VER}.tar.xz \
-C tmp specs || exit 1 ; }
[[ -n ${PP_VER} ]] && {
mv tmp/ssp/protector.patch tmp/ssp/gcc-${gver}-ssp.patch
-tar -Jcf gcc-${gver}-ssp-${PP_VER}.tar.xz \
+tar -acf gcc-${gver}-ssp-${PP_VER}.tar.xz \
-C tmp ssp || exit 1 ; }
[[ -d ${gver}/man ]] && {
-tar -Jcf gcc-${MAN_VER}-manpages.tar.xz \
+tar -acf gcc-${MAN_VER}-manpages.tar.xz \
-C tmp/man . || exit 1 ; }
# extra cruft
[[ -n ${HTB_VER} ]] && {
next reply other threads:[~2022-04-10 11:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 11:37 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-27 16:23 [gentoo-commits] proj/gcc-patches:master commit in: / Sam James
2022-08-27 16:23 Sam James
2022-05-22 23:16 Sam James
2022-04-25 1:12 Sam James
2022-04-10 11:37 Sam James
2022-04-09 3:02 Sam James
2022-01-08 3:49 Sam James
2022-01-08 3:49 Sam James
2022-01-08 3:49 Sam James
2020-12-30 17:26 Sergei Trofimovich
2020-05-28 23:04 Sergei Trofimovich
2020-02-15 19:59 Sergei Trofimovich
2018-08-08 7:54 Sergei Trofimovich
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=1649590640.26c57df5469813c897b8c7d34a969a3dc483e019.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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