Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WLTAU-0004gF-CF for bitcoin-development@lists.sourceforge.net; Thu, 06 Mar 2014 07:56:38 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.46 as permitted sender) client-ip=209.85.214.46; envelope-from=laanwj@gmail.com; helo=mail-bk0-f46.google.com; Received: from mail-bk0-f46.google.com ([209.85.214.46]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WLTAT-0001VW-GE for bitcoin-development@lists.sourceforge.net; Thu, 06 Mar 2014 07:56:38 +0000 Received: by mail-bk0-f46.google.com with SMTP id v15so548508bkz.5 for ; Wed, 05 Mar 2014 23:56:31 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.204.73.2 with SMTP id o2mr39971bkj.55.1394092591069; Wed, 05 Mar 2014 23:56:31 -0800 (PST) Received: by 10.205.75.72 with HTTP; Wed, 5 Mar 2014 23:56:30 -0800 (PST) In-Reply-To: <5317A292.2030102@gmail.com> References: <5317A292.2030102@gmail.com> Date: Thu, 6 Mar 2014 08:56:30 +0100 Message-ID: From: Wladimir To: Kevin Content-Type: multipart/alternative; boundary=047d7b874e4cace2ce04f3eb795a X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WLTAT-0001VW-GE Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Process for getting a patch aproved? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2014 07:56:38 -0000 --047d7b874e4cace2ce04f3eb795a Content-Type: text/plain; charset=UTF-8 On Wed, Mar 5, 2014 at 11:17 PM, Kevin 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 --047d7b874e4cace2ce04f3eb795a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable