Field "Upstream Status" in patch headers

Nico R. n-roeser at gmx.net
Tue Aug 17 02:43:55 PDT 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The page <URL:http://www.linuxfromscratch.org/patches/submit.html> lists
the field "Upstream Status" as mandatory.
I am often unsure what to use as value for this field, and I think it
might be valuable if we made some *suggestions* on that web page. For
example, we could define the following values:
 * Do not submit
 * Not submitted
 * Submitted
 * Not Accepted
 * Accepted
 * Merged

The meaning of them is probably clear to everyone. I assume that people
will start using them if we suggest it, and that could make things a
bit easier.

Currently, I don't know what value to use for a patch that comes from
upstream: I got the official fix from upstream CVS and converted it to
'diff -Naur' format. Yes, the patch is merged upstream, but it also
comes from there. "Merged" would mean to me that I sent the patch
upstream and somebody accepted and merged it. So does "From upstream
CVS" seem more adequate? Suggestions?


Not all our patches currently have that mandatory field. Should we
insert it if it is missing or just keep all patches as-is and only
require it on new patches?

Yours
- -- 
Nico
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFBIdNixI5uhYOGv4URAgpVAJ9p4UHhlY0dgzjulZrJVOEtdxdIeACfa1xK
94KsHA3cEx+dI88TgxPrqBw=
=HWB8
-----END PGP SIGNATURE-----



More information about the patches mailing list