r74 - /web/deps/dep3.mdwn
hertzog at users.alioth.debian.org
hertzog at users.alioth.debian.org
Wed Jul 15 22:12:04 UTC 2009
Author: hertzog
Date: Wed Jul 15 22:12:04 2009
New Revision: 74
URL: http://svn.debian.org/wsvn/dep/?sc=1&rev=74
Log:
Make categorization in Origin optional. Make Origin optional if Author is present.
Modified:
web/deps/dep3.mdwn
Modified: web/deps/dep3.mdwn
URL: http://svn.debian.org/wsvn/dep/web/deps/dep3.mdwn?rev=74&op=diff
==============================================================================
--- web/deps/dep3.mdwn (original)
+++ web/deps/dep3.mdwn Wed Jul 15 22:12:04 2009
@@ -86,29 +86,31 @@
It's recommended to keep each line shorter than 80 characters.
- * `Origin` (required)
+ * `Origin` (required except if `Author` is present)
- This field should document the origin of the patch. It starts with a
- single keyword that can have the following standard values: "upstream"
- (in the case of a patch cherry-picked from the upstream VCS),
- "backport" (in the case of an upstream patch that had to be modified
- to apply on the current version), "vendor" for a patch created
- by Debian or another distribution vendor, or "other" for all other
- kind of patches. It can be optionally followed by a colon with
- leading/trailing spaces before/after it. In that case, all the content
- after the colon contains supplementary information defining in more
- details the origin of the patch. In most cases, it should be a simple
- URL. For patches backported/taken from upstream, it should point into
- the upstream VCS web interface when possible, otherwise it can simply
- list the relevant commit identifier (it should be prefixed with
- "commit:" in that case). For other cases, one should simply indicate
- the URL where the patch got grabbed (mailing list archives,
- distribution bugtrackers, etc.) when possible.
+ This field should document the origin of the patch. In most cases, it
+ should be a simple URL. For patches backported/taken from upstream, it
+ should point into the upstream VCS web interface when possible,
+ otherwise it can simply list the relevant commit identifier (it should
+ be prefixed with "commit:" in that case). For other cases, one should
+ simply indicate the URL where the patch was taken from (mailing list
+ archives, distribution bugtrackers, etc.) when possible.
- In general, a user-created patch grabbed in a BTS should be tagged
- as "other". When copying a patch from another vendor, the
+ The field can be optionaly prefixed with a single keyword followed by
+ a comma and a space to categorize the origin. The allowed keywords are
+ "upstream" (in the case of a patch cherry-picked from the upstream
+ VCS), "backport" (in the case of an upstream patch that had to be
+ modified to apply on the current version), "vendor" for a patch
+ created by Debian or another distribution vendor, or "other" for all
+ other kind of patches.
+
+ In general, a user-created patch grabbed in a BTS should be
+ categorized as "other". When copying a patch from another vendor, the
meta-information (and hence this field) should be kept if present, or
created if necessary with a "vendor" origin.
+
+ If the `Author` field is present, the `Origin` field can be omitted
+ and it's assumed that the patch comes from its author.
* `Bug-<Vendor>` or `Bug` (optional)
@@ -172,3 +174,5 @@
* 2009-06-19: Replace Origin/Status/Patch with Origin/Forwarded. Add new
fields Author and Last-Update. Rename Signed-off-by in Reviewed-by.
Add a paragraph about the scope of the proposal.
+* 2009-07-15: Make categorization in Origin optional. Make Origin optional
+ if Author is present.
More information about the dep-commits
mailing list