https://bugzilla.redhat.com/show_bug.cgi?id=1594313
--- Comment #4 from jiri vanek jvanek@redhat.com --- (In reply to Severin Gehwolf from comment #2)
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).
Agree - I have failed to found the upstream bug, This the stupid name. One more detail - many bugs are duplicated, and it prove itself to have the name convention in
JDKID-PRID-RHBZID-name.patch
as all those thre ids aree usually necessary.