From: David Ward on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547864291 We can't rely on that, because a date is only used for snapshotting. `kernel-5.12.0-0.rc6.184` does not have a date in it, but everything you mentioned still applies; you could rebuild the same source with a new tag after making configuration fixes. My understanding is that `<N>` is supposed to be the field that distinguish changes in dist-git the way you described. Yes, it is redundant to have both a date and a commit hash, but [it was meant](https://docs.fedoraproject.org/en-US/packaging- guidelines/Versioning/#_snapshots) to be that way: > All snapshots MUST contain a snapshot information field (`<snapinfo>:`) in the Release: tag. That field must at minimum consist of the date in eight-digit "YYYYMMDD" format. The packager MAY include up to 17 characters of additional information after the date. The following formats are suggested: > > `YYYYMMDD.<revision>` > > `YYYYMMDD<scm><revision>` Again, I'm just making sure I understand how this is expected to work now, and if it should be different based on the Fedora Versioning Guidelines or any other reason. I can open a MR for changes that make sense. _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
