From: Wladimir <laanwj@gmail•com>
To: Kevin <kevinsisco61784@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Process for getting a patch aproved?
Date: Thu, 6 Mar 2014 08:56:30 +0100 [thread overview]
Message-ID: <CA+s+GJA7V1hGRxYr0f7a8hPEnY-+AqeTPZVQ6WzOLCo-n6ayLg@mail.gmail.com> (raw)
In-Reply-To: <5317A292.2030102@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
On Wed, Mar 5, 2014 at 11:17 PM, Kevin <kevinsisco61784@gmail•com> wrote:
> Hello. How would I submit a patch? Could it be sent through the list
> as an attachment?
>
You can, but as reviewing can take a while, the github model works better
for this project.
In my experience people lose track of patches sent to mailing lists, at
least when posted to github there will be a nagging 'issue' appearing until
it is either merged or closed otherwise.
If it concerns a proposed protocol change do discuss it on the mailing
list, as people building other implementations read here and not on github.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1042 bytes --]
prev parent reply other threads:[~2014-03-06 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 22:17 Kevin
2014-03-05 22:27 ` Gregory Maxwell
2014-03-06 7:56 ` Wladimir [this message]
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+GJA7V1hGRxYr0f7a8hPEnY-+AqeTPZVQ6WzOLCo-n6ayLg@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=kevinsisco61784@gmail$(echo .)com \
/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