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

[Sebastian Huber (@sebhub)]

Sebastian Huber commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/288#note_114531


We had the long version for quite a while. In the commit message, there are three issues with the short version:

1. Existing support code may rely on this.
2. The short hash is generated based on the current repository state. The reported hash should be useful also for future states of the repository
3. If Git changes the hash algorithm in the future, then the hash length may be used as an indicator for the hash algorithm. With a variable hash length this is more difficult.

For the Git hash change, see https://git-scm.com/docs/hash-function-transition.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/288#note_114531
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/20241108/b3a8b311/attachment.htm>