highperfocused/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-17 21:32:50 +01:00
Code Issues Packages Projects Releases Wiki Activity

bip-0002: Allow Post-History header to be a link as with BIPs 99, 122, and 124

Browse Source
This commit is contained in:
Luke Dashjr 2016-09-24 04:11:10 +00:00
parent 7ca7445c80
commit 44f85187fe
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bip-0002.mediawiki
View File

@ -149,7 +149,7 @@ Each BIP must begin with an RFC 822 style header preamble. The headers must appe
Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
License: <abbreviation for approved license(s)>
* License-Code: <abbreviation for code under different approved license(s)>
* Post-History: <dates of postings to bitcoin mailing list>
* Post-History: <dates of postings to bitcoin mailing list, or link to thread in mailing list archive>
* Replaces: <BIP number>
* Superseded-By: <BIP number>
</pre>
@ -165,7 +165,9 @@ While a BIP is in private discussions (usually during the initial Draft phase),
The Type header specifies the type of BIP: Standards Track, Informational, or Process.
The Created header records the date that the BIP was assigned a number, while Post-History is used to record the dates of when new versions of the BIP are posted to bitcoin mailing lists. Both headers should be in yyyy-mm-dd format, e.g. 2001-08-14.
The Created header records the date that the BIP was assigned a number, while Post-History is used to record when new versions of the BIP are posted to bitcoin mailing lists.
Dates should be in yyyy-mm-dd format, e.g. 2001-08-14.
Post-History is permitted to be a link to a specific thread in a mailing list archive.
BIPs may have a Requires header, indicating the BIP numbers that this BIP depends on.