From: Wladimir <laanwj@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Do not use github issues on BIPs repository
Date: Fri, 6 Jun 2014 06:05:32 +0200 [thread overview]
Message-ID: <CA+s+GJA9ki6RUZ8S3wRW5Pev-COSotkVkL=b_6DHZnCnW4j45Q@mail.gmail.com> (raw)
Hello,
I see that people have been filing issues on the Bitcoin Improvement
Requests repository, https://github.com/bitcoin/bips.
This is not how it is supposed to work -- BIP authors are not required
to monitor the github issues, and it is not a good place to discuss in
the first place. If you have a remark about a BIP or want to discuss
it please use this mailing list (preferably) or contact the authors
some other way.
After discussion you can submit a pull request. Or if the change is
trivial, such as a typo, you can submit a pull immediately.
For this reason I intend to disable issues (not pull requests, of
course) on the repository.
Wladimir
reply other threads:[~2014-06-06 4:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+s+GJA9ki6RUZ8S3wRW5Pev-COSotkVkL=b_6DHZnCnW4j45Q@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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