Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qdvdx-0000V9-FU for bitcoin-development@lists.sourceforge.net; Tue, 05 Jul 2011 02:45:45 +0000 X-ACL-Warn: Received: from mail-iy0-f175.google.com ([209.85.210.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Qdvdw-00079f-5M for bitcoin-development@lists.sourceforge.net; Tue, 05 Jul 2011 02:45:45 +0000 Received: by iym10 with SMTP id 10so6848884iym.34 for ; Mon, 04 Jul 2011 19:45:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.115.142 with SMTP id i14mr6032260ibq.139.1309833938450; Mon, 04 Jul 2011 19:45:38 -0700 (PDT) Received: by 10.231.37.3 with HTTP; Mon, 4 Jul 2011 19:45:38 -0700 (PDT) X-Originating-IP: [99.173.148.118] In-Reply-To: References: <1309801974.3423.80.camel@Desktop666> <1309811972.29355.19.camel@Desktop666> <1309828239.29355.28.camel@Desktop666> Date: Mon, 4 Jul 2011 22:45:38 -0400 Message-ID: From: Jeff Garzik To: Gavin Andresen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1Qdvdw-00079f-5M Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Encrypted Wallet Backward Compatibility 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: Tue, 05 Jul 2011 02:45:45 -0000 On Mon, Jul 4, 2011 at 10:26 PM, Gavin Andresen w= rote: >> All that needs to happen for that is to agree on either >> https://github.com/bitcoin/bitcoin/pull/378 or >> https://github.com/bitcoin/bitcoin/pull/381' > > I don't think 0.3.24 "needs" either of those pulls. =A0Fixing > downgrade-to-0.3.24 is low on the priority list, because > downgrade-to-something-before-0.3.24 is just about as likely, and that > has to do something mostly reasonable. Yeah, same thoughts here. > I just pulled https://github.com/bitcoin/bitcoin/pull/379 "Do not use > comma as thousands separator", and pulled a block-chain lock-in at > block 13444. =A0Those were the only issues I think really need to be in > 0.3.24. Tagged -tip as -rc2. Bug reports are mostly quiet, so maybe we can even get the release before you leave. --=20 Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com