From mboxrd@z Thu Jan  1 00:00:00 1970
From: Masahiro Yamada <yamada.m@jp.panasonic.com>
Date: Thu, 17 Apr 2014 20:41:14 +0900
Subject: [U-Boot] [PATCH 0/5] Do not use __DATE__ and __TIME__ anymore
In-Reply-To: <20140417110732.85F553803FE@gemini.denx.de>
References: <1397721632-18797-1-git-send-email-yamada.m@jp.panasonic.com>
	<20140417110732.85F553803FE@gemini.denx.de>
Message-ID: <20140417204113.6CEC.AA925319@jp.panasonic.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Wolfgang

On Thu, 17 Apr 2014 13:07:32 +0200
Wolfgang Denk <wd@denx.de> wrote:

> Dear Masahiro,
> 
> In message <1397721632-18797-1-git-send-email-yamada.m@jp.panasonic.com> you wrote:
> > 
> > The aim of this series is to prohibit using __DATE__ and __TIME__.
> 
> What is bad about using these?


include/generated/timestamp_autogenerated.h provides us
the last build date correctly because it is touched every time.

__DATE__ or __TIME__ might give us unexpectedly old date
because it is not updated unless the source file is modified.


One more reason.
Using __DATE__ / __TIME__  here and there makes the binary
comparison difficult.

I often use MD5SUM comparison
to confirm that my changes to the build system still produce the same
output.

I want to generate the completely same result
if the source code is the same.

This can be achieved by simply disabling the timestamp file  and version
file.
I want to gather timestamp stuff to one place for easy control of it.



Best Regards
Masahiro Yamada