glibc/template.patch

Short description: <Short description>
Author(s): <Who wrote them. Comma separated.>
Origin: <Source repo(s) where it came from or keyword "PATCH" if this is simply a patch>
# Likely git://sourceware.org/git/glibc.git
Bug-RHEL: <Rhel bug #'s, comma separated e.g. #XXX, #YYY, #ZZZ>
Bug-Fedora: <Fedora bug #'s, comma separated e.g. #XXX, #YYY, #ZZZ>
Bug-Upstream: <Upstream bug#'s, comma separated e.g. #XXX, #YYY, #ZZZ>
Upstream status: <[Patchwork URL|libc-alpha URL|not-needed|not-submitted|committed] for each commit>
# <Additional descriptive text follows 'Upstream status:' line>
<If upstream status == committed then a copy of the upstream commit log follows>
<Patch>
glibc.spec: Apply patches in logical order. The following commit removes the requirement for patches to be placed in 1000, 2000, or 3000 ID blocks depending on their upstream status. Instead upstream status is documented in the header of the patch with some semi-standard notation as described in template.patch. The patches are re-numbered and defined and applied in the same order. Verified that before and after the patch that the source tree does not change. The patch definition is resorted to match the patch application order. 2018-04-17 19:55:54 +00:00			`Short description: <Short description>`
			`Author(s): <Who wrote them. Comma separated.>`
			`Origin: <Source repo(s) where it came from or keyword "PATCH" if this is simply a patch>`
			`# Likely git://sourceware.org/git/glibc.git`
			`Bug-RHEL: <Rhel bug #'s, comma separated e.g. #XXX, #YYY, #ZZZ>`
			`Bug-Fedora: <Fedora bug #'s, comma separated e.g. #XXX, #YYY, #ZZZ>`
			`Bug-Upstream: <Upstream bug#'s, comma separated e.g. #XXX, #YYY, #ZZZ>`
			`Upstream status: <[Patchwork URL\|libc-alpha URL\|not-needed\|not-submitted\|committed] for each commit>`
			`# <Additional descriptive text follows 'Upstream status:' line>`
			`<If upstream status == committed then a copy of the upstream commit log follows>`
			`<Patch>`