From: Gavin Andresen <gavinandresen@gmail.com>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git repository
Date: Fri, 6 Dec 2013 09:16:47 +1000 [thread overview]
Message-ID: <CABsx9T2v5OBwh55s=5HmzU0HLyvg8e=FGUFit0Zp6V6nUfLB2A@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
RE: replace BIPs on the wiki with links to github documents: agreed.
Wladimir or Gregory: can one of you update BIP 0001 to describe the Proper
Process for creating/editing a BIP? It doesn't mention the github repo at
all right now.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 365 bytes --]
next prev parent reply other threads:[~2013-12-05 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 13:37 [Bitcoin-development] Move authorative source for BIPs to git repository Wladimir
2013-12-05 14:27 ` Luke-Jr
2013-12-05 14:38 ` Wladimir
2013-12-05 14:43 ` Jeff Garzik
2013-12-05 20:49 ` Gary Rowe
2013-12-05 23:16 ` Gavin Andresen [this message]
2013-12-06 13:41 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABsx9T2v5OBwh55s=5HmzU0HLyvg8e=FGUFit0Zp6V6nUfLB2A@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=laanwj@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox