From: John Kacur <jkacur@redhat.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Clark Williams <clark.williams@gmail.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH rt-tests] pi_stress: remove timestamp of compilation from version output
Date: Tue, 17 Feb 2015 17:46:45 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.10.1502171745580.15981@riemann> (raw)
In-Reply-To: <1424185739-29680-1-git-send-email-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1042 bytes --]
On Tue, 17 Feb 2015, Uwe Kleine-König wrote:
> Having the date and time of compilation is hardly useful and is in the
> way for reproducible building binaries.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
>
> a few people work on getting reproducible builds for Debian. Using
> __DATE__ and __TIME__ obviously makes the rt-tests package fail to
> compile in a deterministic fashion.
>
> Best regards
> Uwe
>
> src/pi_tests/pi_stress.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/src/pi_tests/pi_stress.c b/src/pi_tests/pi_stress.c
> index e273d62..9b33fad 100644
> --- a/src/pi_tests/pi_stress.c
> +++ b/src/pi_tests/pi_stress.c
> @@ -1235,7 +1235,6 @@ void process_command_line(int argc, char **argv)
> break;
> case 'V':
> printf("pi_stress v%1.2f ", VERSION_STRING);
> - printf("(%s %s)\n", __DATE__, __TIME__);
> exit(0);
> case 'u':
> uniprocessor = 1;
> --
> 2.1.4
>
> --
This patch is okay with me.
Signed-off-by: John Kacur <jkacur@redhat.com>>
next prev parent reply other threads:[~2015-02-17 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 15:08 [PATCH rt-tests] pi_stress: remove timestamp of compilation from version output Uwe Kleine-König
2015-02-17 16:46 ` John Kacur [this message]
2015-02-17 18:03 ` Sebastian Andrzej Siewior
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=alpine.LFD.2.10.1502171745580.15981@riemann \
--to=jkacur@redhat.com \
--cc=clark.williams@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.