RTEMS | build: Report normal Git hash (!288)

[Chris Johns (@chris)]

Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/288#note_115130


This MR was discussed in the last weekly meeting and @sebhub said only a full hash defines the commit and if a short hash is captured you can only assume it matches the full hash. You can never recover the full hash. This is not an issue when using releases however if you are using a workflow based around placing code from git into production then the full hash is important.

@gedare is it OK to change this MR to %"6.1" ?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/288#note_115130
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20241117/8b9dc8a7/attachment-0001.htm>