summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Dashjr <luke-jr+git@utopios.org>2016-09-24 04:08:58 +0000
committerLuke Dashjr <luke-jr+git@utopios.org>2016-09-24 06:27:08 +0000
commit7ca7445c80016fb7569903569338abb802ae742c (patch)
treebbf3df266e4ea8132bf4ac8806a6e8c32f61dead
parent9b040c5042a21a5bee06df4974d32cf10545c1c6 (diff)
downloadbips-7ca7445c80016fb7569903569338abb802ae742c.tar.xz
bip-0002: Drop unused and inapplicable Resolution header from preamble
-rw-r--r--bip-0002.mediawiki3
1 files changed, 0 insertions, 3 deletions
diff --git a/bip-0002.mediawiki b/bip-0002.mediawiki
index 9a05fed..83b027c 100644
--- a/bip-0002.mediawiki
+++ b/bip-0002.mediawiki
@@ -152,7 +152,6 @@ Each BIP must begin with an RFC 822 style header preamble. The headers must appe
* Post-History: <dates of postings to bitcoin mailing list>
* Replaces: <BIP number>
* Superseded-By: <BIP number>
-* Resolution: <url>
</pre>
The Author header lists the names and email addresses of all the authors/owners of the BIP.
@@ -162,8 +161,6 @@ The format of the Author header value must be
If there are multiple authors, each should be on a separate line following RFC 2822 continuation line conventions.
-Note: The Resolution header is required for Standards Track BIPs only. It contains a URL that should point to an email message or other web resource where the pronouncement about the BIP is made.
-
While a BIP is in private discussions (usually during the initial Draft phase), a Discussions-To header will indicate the mailing list or URL where the BIP is being discussed. No Discussions-To header is necessary if the BIP is being discussed privately with the author, or on the bitcoin email mailing lists.
The Type header specifies the type of BIP: Standards Track, Informational, or Process.