From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
Clark Williams <williams@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>
Subject: Re: [PATCH 5/6] Change VERSION_STRING to VERSION
Date: Tue, 14 Jul 2015 18:09:37 +0200 [thread overview]
Message-ID: <20150714160937.GF21820@linutronix.de> (raw)
In-Reply-To: <1436531131-9186-6-git-send-email-jkacur@redhat.com>
* John Kacur | 2015-07-10 14:25:30 [+0200]:
>Adding _STRING doesn't add any extra meaning, but the extra length makes
>the Makefile more unreadable than is necessary, so shorten this up
It isn't a STRING to begin with. You could use __stringify() to make a
string out of it. Not sure if -D=\"VERSION\" works as expected. This
would also get rid of the "overflow" with 0.100 that was mentioned in
the thread…
>diff --git a/Makefile b/Makefile
>index a48e7597b908..1f7640b82fa6 100644
>--- a/Makefile
>+++ b/Makefile
>@@ -158,23 +158,23 @@ release: distclean changelog
> mkdir -p releases
> mkdir -p tmp/rt-tests
> cp -r Makefile COPYING ChangeLog MAINTAINERS doc README.markdown src tmp/rt-tests
>- rm -f rt-tests-$(VERSION_STRING).tar rt-tests-$(VERSION_STRING).tar.asc
>- tar -C tmp -cf rt-tests-$(VERSION_STRING).tar rt-tests
>- gpg2 --default-key clrkwllms@kernel.org --detach-sign --armor rt-tests-$(VERSION_STRING).tar
>- gzip rt-tests-$(VERSION_STRING).tar
>+ rm -f rt-tests-$(VERSION).tar rt-tests-$(VERSION).tar.asc
>+ tar -C tmp -cf rt-tests-$(VERSION).tar rt-tests
>+ gpg2 --default-key clrkwllms@kernel.org --detach-sign --armor rt-tests-$(VERSION).tar
>+ gzip rt-tests-$(VERSION).tar
> rm -f ChangeLog
>- cp rt-tests-$(VERSION_STRING).tar.gz rt-tests-$(VERSION_STRING).tar.asc releases
>+ cp rt-tests-$(VERSION).tar.gz rt-tests-$(VERSION).tar.asc releases
Is this target in use? I doubt you use Clark's key. You could remove the
--default-key option and have default-key in ~/.gnupg/gpg.conf.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-14 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 12:25 [PATCH 0/6] Various rt-test patches John Kacur
2015-07-10 12:25 ` [PATCH 1/6] Fix warning: unused variable ‘c’ John Kacur
2015-07-10 12:25 ` [PATCH 2/6] Fix possible exit on error without releasing mutex John Kacur
2015-07-14 15:59 ` Sebastian Andrzej Siewior
2015-07-14 21:03 ` John Kacur
2015-07-10 12:25 ` [PATCH 3/6] Create a .gitattribute file to specify what files git-archive should ignore John Kacur
2015-07-10 12:25 ` [PATCH 4/6] Add .tar files to .gitignore John Kacur
2015-07-14 15:58 ` Sebastian Andrzej Siewior
2015-07-14 20:33 ` John Kacur
2015-07-10 12:25 ` [PATCH 5/6] Change VERSION_STRING to VERSION John Kacur
2015-07-10 13:42 ` Pavel Vasilyev
2015-07-14 16:09 ` Sebastian Andrzej Siewior [this message]
2015-07-14 21:45 ` John Kacur
2015-07-10 12:25 ` [PATCH 6/6] Create an rt-tests.tar file using git-archive John Kacur
2015-07-14 16:13 ` Sebastian Andrzej Siewior
2015-07-14 20:28 ` John Kacur
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=20150714160937.GF21820@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).