From 7fe46616d531429d0091cd8efb29660ccfb728ed Mon Sep 17 00:00:00 2001 From: Rafael Fontenelle Date: Mar 31 2021 15:01:18 +0000 Subject: PatchUpstreamStatus: Add title and adjust levels Add titles to avoid "Untitled" in page title, and adjust headers for sequential level --- diff --git a/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc b/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc index 13b3646..825abdd 100644 --- a/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc +++ b/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc @@ -1,4 +1,6 @@ -=== All patches should have an upstream bug link or comment += Patch status + +== All patches should have an upstream bug link or comment All patches in Fedora spec files *SHOULD* have a comment above them about their upstream status. Any time you create a patch, it is best practice to file it in an upstream bug tracker, and include a link to that in the comment above the patch. For example: @@ -17,7 +19,7 @@ Patch0: gnome-panel-fix-frobnicator.patch Sending patches upstream and adding this comment will help ensure that Fedora is acting as a good FLOSS citizen (see https://fedoraproject.org/wiki/Staying_close_to_upstream_projects[Staying close to upstream projects]). It will help others (and even you) down the line in package maintenance by knowing what patches are likely to appear in a new upstream release. -==== If upstream doesn't have a bug tracker +=== If upstream doesn't have a bug tracker You can indicate that you have sent the patch upstream and any known status: @@ -31,7 +33,7 @@ Patch0: foobar-fix-the-bar.patch Patch0: foobar-fix-the-baz.patch .... -==== Fedora-specific (or rejected upstream) patches +=== Fedora-specific (or rejected upstream) patches It may be that some patches truly are Fedora-specific; in that case, say so: