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

[Gedare Bloom (@gedare)]

Gedare Bloom commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/288#note_115151


I linked the wrong place: https://git-scm.com/docs/git-config#Documentation/git-config.txt-coreabbrev

The command already gives different length short commits in our various repositories, because the appropriate size is inferred by the size of the repo. I get back 11 characters for rtems.git. So for sure an explicit size needs to be set. But any size we set eventually has to be increased to avoid conflicts.

I don't understand what you mean by "have both stored" because this change is about the release label, which is a string used to identify a release. There's no difference between what you display and what you use. 

The change here is about what goes in the release label. The release label requires uniqueness and the ability to invert it to get back to the point where the release was made. 

We can resolve this thread with an Issue against milestone 7.1.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/288#note_115151
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/20241118/44e8ffcf/attachment-0001.htm>