public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [Bitcoin-development] Process for getting a patch aproved?
@ 2014-03-05 22:17 Kevin
  2014-03-05 22:27 ` Gregory Maxwell
  2014-03-06  7:56 ` Wladimir
  0 siblings, 2 replies; 3+ messages in thread
From: Kevin @ 2014-03-05 22:17 UTC (permalink / raw)
  To: bitcoin-development

Hello.  How would I submit a patch?  Could it be sent through the list 
as an attachment?

-- 
Kevin




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Bitcoin-development] Process for getting a patch aproved?
  2014-03-05 22:17 [Bitcoin-development] Process for getting a patch aproved? Kevin
@ 2014-03-05 22:27 ` Gregory Maxwell
  2014-03-06  7:56 ` Wladimir
  1 sibling, 0 replies; 3+ messages in thread
From: Gregory Maxwell @ 2014-03-05 22:27 UTC (permalink / raw)
  To: Kevin; +Cc: Bitcoin Development

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.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Bitcoin-development] Process for getting a patch aproved?
  2014-03-05 22:17 [Bitcoin-development] Process for getting a patch aproved? Kevin
  2014-03-05 22:27 ` Gregory Maxwell
@ 2014-03-06  7:56 ` Wladimir
  1 sibling, 0 replies; 3+ messages in thread
From: Wladimir @ 2014-03-06  7:56 UTC (permalink / raw)
  To: Kevin; +Cc: Bitcoin Dev

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-03-06  7:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-05 22:17 [Bitcoin-development] Process for getting a patch aproved? Kevin
2014-03-05 22:27 ` Gregory Maxwell
2014-03-06  7:56 ` Wladimir

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox