[Bitcoin-development] Process for getting a patch aproved?
Hello. How would I submit a patch? Could it be sent through the list as an attachment? -- Kevin -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Process for getting a patch aproved?
On Wed, Mar 5, 2014 at 2:17 PM, Kevin kevinsisco61...@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. -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Process for getting a patch aproved?
On Wed, Mar 5, 2014 at 11:17 PM, Kevin kevinsisco61...@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 -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development