Packaging:PatchUpstreamStatus

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:

Patch0: gnome-panel-fix-frobnicator.patch
 * 1) http://bugzilla.gnome.org/show_bug.cgi?id=12345

The above is perfectly acceptable; but if you prefer, a brief comment about what the patch does above can be helpful:

Patch0: gnome-panel-fix-frobnicator.patch
 * 1) Don't crash with frobnicator applet
 * 2) http://bugzilla.gnome.org/show_bug.cgi?id=12345

Sending patches upstream and adding this comment will help ensure that Fedora is acting as a good FLOSS citizen (see  Why Upstream? ). 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
You can indicate that you have sent the patch upstream and any known status:

Patch0: foobar-fix-the-bar.patch
 * 1) Sent upstream via email 20080407

Patch0: foobar-fix-the-baz.patch
 * 1) Upstream has applied this in SVN trunk

Fedora-specific (or rejected upstream) patches
It may be that some patches truly are Fedora-specific; in that case, say so:

Patch0: jna-jni-path.patch
 * 1) This patch is temporary until we land the long term System.loadLibrary fix in OpenJDK

= Why upstream? =

Refer  Why Upstream?