From 44f85187fe06444d83d9a7250eedb66ebdb6bde2 Mon Sep 17 00:00:00 2001
From: Luke Dashjr <luke-jr+git@utopios.org>
Date: Sat, 24 Sep 2016 04:11:10 +0000
Subject: bip-0002: Allow Post-History header to be a link as with BIPs 99,
 122, and 124

---
 bip-0002.mediawiki | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/bip-0002.mediawiki b/bip-0002.mediawiki
index 83b027c..5455419 100644
--- a/bip-0002.mediawiki
+++ b/bip-0002.mediawiki
@@ -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.
 
-- 
cgit v1.2.3