From: Gregory Maxwell <gmaxwell@gmail•com>
To: Kevin <kevinsisco61784@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Process for getting a patch aproved?
Date: Wed, 5 Mar 2014 14:27:13 -0800 [thread overview]
Message-ID: <CAAS2fgRBb8c-8ghQEJj9Sq+4Ai9LkQ2CU_fZV7dXUHHG+-=dDA@mail.gmail.com> (raw)
In-Reply-To: <5317A292.2030102@gmail.com>
On Wed, Mar 5, 2014 at 2:17 PM, Kevin <kevinsisco61784@gmail•com> wrote:
> Hello. How would I submit a patch? Could it be sent through the list
> as an attachment?
To the reference software? Normally you'd open a github account and
submit there.
Though if for some reason you can't— though its strongly preferred—
sending a git-format-patch via email might be an acceptable fallback.
next prev parent reply other threads:[~2014-03-05 22:27 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 [this message]
2014-03-06 7:56 ` 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='CAAS2fgRBb8c-8ghQEJj9Sq+4Ai9LkQ2CU_fZV7dXUHHG+-=dDA@mail.gmail.com' \
--to=gmaxwell@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