From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH][RFC] Update U-Boot's build timestamp on every compile
Date: Tue, 21 Oct 2008 14:03:06 -0500 [thread overview]
Message-ID: <1224615786.18428.389.camel@localhost.localdomain> (raw)
In-Reply-To: <2acbd3e40810211152q150501b7t5e001b875279d1f9@mail.gmail.com>
Hi Andy,
> I don't think he's wanting this as much for releases (which would be
> fine with the git id as you mentioned), but during the development
> process. It is very useful during development to have a timestamp
> which confirms that what you are running now is what you expect.
> There are various ways I have used this:
>
> * Catch that I failed to copy the new image to my tftp directory
> * Confirm that I'm booting from the flash bank I just programmed
> * Helpful for figuring out which of the files in my tftp directory
> corresponds to what's running
100% agree - all our releases are generated from fully-committed git
trees with tags. This patch only intends to improve development.
> Also, while I can see good arguments for not having a time stamp,
> having one that is not up-to-date seems totally useless. The stamp
> might not be updated for months, and thus provides only an indicator
> as to when the date was last updated.
>
> Upshot: I endorse this patch's concept, and urge Peter to put in his
> (apparently underpaid) time to complete it. :)
I'll submit a patch shortly. I'll also mention the underpaid comment to
management and see what comes of that;)
Peter
prev parent reply other threads:[~2008-10-21 19:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 22:51 [U-Boot] [PATCH][RFC] Update U-Boot's build timestamp on every compile Peter Tyser
2008-10-17 22:55 ` Peter Tyser
2008-10-21 0:59 ` Kim Phillips
2008-10-21 2:02 ` Peter Tyser
2008-10-21 7:04 ` Wolfgang Denk
2008-10-21 14:40 ` Peter Tyser
2008-10-21 14:51 ` Jerry Van Baren
2008-10-21 15:02 ` Wolfgang Denk
2008-10-21 15:17 ` Peter Tyser
2008-10-21 14:57 ` Stefan Roese
2008-10-21 15:04 ` Wolfgang Denk
2008-10-21 14:59 ` Wolfgang Denk
2008-10-21 18:52 ` Andy Fleming
2008-10-21 19:03 ` Peter Tyser [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=1224615786.18428.389.camel@localhost.localdomain \
--to=ptyser@xes-inc.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox