From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] compile-i386: Use SPARSE_VERSION instead of __DATE__
Date: Mon, 2 Oct 2017 21:47:20 +0200 [thread overview]
Message-ID: <20171002194717.hfgwkgrzcf2nuefo@ltop.local> (raw)
In-Reply-To: <20170922081410.29162-1-uwe@kleine-koenig.org>
On Fri, Sep 22, 2017 at 10:14:10AM +0200, Uwe Kleine-König wrote:
> The compile date isn't very informative for a tool, the version is what really
> matters. Additionally using __DATE__ makes the build unreprodicible.
>
Acked-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
prev parent reply other threads:[~2017-10-02 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 8:14 [PATCH] compile-i386: Use SPARSE_VERSION instead of __DATE__ Uwe Kleine-König
2017-10-02 19:47 ` Luc Van Oostenryck [this message]
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=20171002194717.hfgwkgrzcf2nuefo@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=uwe@kleine-koenig.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