Fwd: [openbmc/phosphor-host-ipmid] BMC version should be BCD encoded (#89)

[Adriana Kobylak]

Any thoughts on the concern about BMC version being decimal, so that the IPMI representation of the version in BCD does not match character by character the tag in github?
Should we limit the tag numbering to a max digit of 9 which would match the decimal and BCD representation, should the tag be in hex, or there should not be any change and this is how it works, other?


> Begin forwarded message:
> 
> From: John Wang <notifications at github.com>
> Subject: Re: [openbmc/phosphor-host-ipmid] BMC version should be BCD encoded (#89)
> Date: June 20, 2016 at 10:20:47 PM CDT
> To: openbmc/phosphor-host-ipmid <phosphor-host-ipmid at noreply.github.com>
> Cc: Adriana Kobylak <anoo at linux.vnet.ibm.com>, State change <state_change at noreply.github.com>
> Reply-To: openbmc/phosphor-host-ipmid <reply+008a216f5c58e903296c17b81a4b7ad00c03eaed56ed5c7a92cf000000011380748f92a169ce0962da32 at reply.github.com>
> 
> It'll get confusion if the tag name is not the same as version in response data.
> For example that you mentioned above, the user/designer get the version 0.11 on a failure board and want to track the source code in the tag from GitHub. They won't find out 0.11 tag name in this case. The tag name on GitHub is 0.17 actually.
> 
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub <https://github.com/openbmc/phosphor-host-ipmid/issues/89#issuecomment-227330539>, or mute the thread <https://github.com/notifications/unsubscribe/AIohb8z6mavEWUhhIWYbB4SfyfKFn7FGks5qN1iPgaJpZM4Ipq2v>.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160621/695f2630/attachment.html>