https://bugzilla.redhat.com/show_bug.cgi?id=1594313 --- Comment #2 from Severin Gehwolf <sgehwolf@xxxxxxxxxx> --- Patch6: systemLcmsAndJpgFixFor-f0aeede1b855.patch We should start sticking to a better naming scheme for patches. This one is an upstream bug and, thus, we need to create an upstream bug if there doesn't exist one yet. In this case it's: https://bugs.openjdk.java.net/browse/JDK-8205616 Suggested naming conventions for upstream bugs: JDK-<id>-some-name-with-hyphens.patch Similarly for downstream-only patches, we need to have a RHBZ bug for each patch. Suggested naming convention: RHBZ-<id>-some-name-with-hyphens.patch Sticking to some agreed upon naming convention makes archaeology for patches easier. What's more, it gets easier to track the upstream status for them (if any). -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx/message/OFF2IMVT5MKD2YCF6OFUMJK7NZ6GEFMZ/
