Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1WLKHY-0002vA-Ml
	for bitcoin-development@lists.sourceforge.net;
	Wed, 05 Mar 2014 22:27:20 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.170 as permitted sender)
	client-ip=209.85.217.170; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f170.google.com; 
Received: from mail-lb0-f170.google.com ([209.85.217.170])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WLKHX-0004Vz-Ux
	for bitcoin-development@lists.sourceforge.net;
	Wed, 05 Mar 2014 22:27:20 +0000
Received: by mail-lb0-f170.google.com with SMTP id s7so1185635lbd.1
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 05 Mar 2014 14:27:13 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.136.71 with SMTP id py7mr1567010lbb.26.1394058433421;
	Wed, 05 Mar 2014 14:27:13 -0800 (PST)
Received: by 10.112.189.164 with HTTP; Wed, 5 Mar 2014 14:27:13 -0800 (PST)
In-Reply-To: <5317A292.2030102@gmail.com>
References: <5317A292.2030102@gmail.com>
Date: Wed, 5 Mar 2014 14:27:13 -0800
Message-ID: <CAAS2fgRBb8c-8ghQEJj9Sq+4Ai9LkQ2CU_fZV7dXUHHG+-=dDA@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Kevin <kevinsisco61784@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
	(gmaxwell[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-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: 1WLKHX-0004Vz-Ux
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 05 Mar 2014 22:27:20 -0000

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=E2=80=94 though its strongly preferred=
=E2=80=94
sending a git-format-patch via email might be an acceptable fallback.