All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.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 10:51:57 -0400	[thread overview]
Message-ID: <48FDEC8D.6010502@ge.com> (raw)
In-Reply-To: <1224600029.18428.339.camel@localhost.localdomain>

Peter Tyser wrote:
> Hi Wolfgang,

[big snip]

> I use git, but its version strings only change when commits occur.  I
> think having an accurate build time stamp would be a nice feature.
> FWIW, Linux handles this "issue" very similarly to my proposed solution
> so that it can have its pretty banner.  It even takes it a step further
> and gives a specific compile number (#15):
> 
> Linux version 2.6.23.17 (ptyser at ptyser) (gcc version 4.3.1
> (crosstool-NG-xes) ) #15 SMP Wed Aug 6 11:45:55 CDT 2008
> 
> 
> I know this patch isn't a big deal, but I think it would be a valuable
> change.  If others don't agree I'll drop the issue.
> 
> Thanks,
> Peter

+1
Call me old fashioned, but I like time/date stamps.  They are more 
meaningful to me as a quick "did I really load a new u-boot" or "when 
did I do *that*" than a git hash.

Cost: $0.00.  Benefit: $0.02.  Benefit/Cost = priceless.

FWIIW,
gvb

  reply	other threads:[~2008-10-21 14:51 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 [this message]
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

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=48FDEC8D.6010502@ge.com \
    --to=gerald.vanbaren@ge.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 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.