From: Kevin <kevinsisco61784@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Process for getting a patch aproved?
Date: Wed, 05 Mar 2014 17:17:54 -0500 [thread overview]
Message-ID: <5317A292.2030102@gmail.com> (raw)
Hello. How would I submit a patch? Could it be sent through the list
as an attachment?
--
Kevin
next reply other threads:[~2014-03-05 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 22:17 Kevin [this message]
2014-03-05 22:27 ` [Bitcoin-development] Process for getting a patch aproved? Gregory Maxwell
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=5317A292.2030102@gmail.com \
--to=kevinsisco61784@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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