<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Dear Joseph & Vijay Khemka,</div><div><br></div><div>No matter what your version is, build date only represents the time when the image was created.</div><br><div>thanks,</div><div>Byron</div><br><br><div style="position:relative;zoom:1"></div><div id="divNeteaseMailCard"></div><br><pre><br>At 2019-11-21 02:08:40, "Vijay Khemka" <vijaykhemka@fb.com> wrote:
>
>
>On 11/20/19, 8:40 AM, "openbmc on behalf of Joseph Reynolds" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of jrey@linux.ibm.com> wrote:
>
>
> On 11/18/19 7:23 PM, www wrote:
> > Dear Joseph,
> >
> > Thank you very much for your help. I just want to show the compile
> > time of firmware to the user. If only show the version, it can't
> > correspond to the time. When both are displayed at the same time, the
> > information will be clearer. thanks again.
> >
>
> Byron, thanks for that. I think I understand your use case. However,
> does this practice assume the build date is close to the date when the
> software version was created?
> - For example, I assume you'll merge a git commit to create a new
> software version, and then build an image based on that commit. In this
> way, the build date correlates closely with the version.
> - However, if you build an image from an older commit, or wait a long
> time before building an image, the build date will not correlate closely
> with the version. This can be misleading and lead to errors in handling
> images.
>
>I guess build date should be the date version was released or created.
>
> Is that a concern for you?
>
> - Joseph
>
> > thanks,
> > Byron
> >
> ...snip...
>
>
>
</pre></div><br><br><span title="neteasefooter"><p> </p></span>