From mboxrd@z Thu Jan 1 00:00:00 1970 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 1Qp4kP-0005mI-U9 for bitcoin-development@lists.sourceforge.net; Thu, 04 Aug 2011 20:42:29 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Qp4kK-00069y-7I for bitcoin-development@lists.sourceforge.net; Thu, 04 Aug 2011 20:42:29 +0000 Received: from ishibashi.localnet (fl-67-77-87-241.dhcp.embarqhsd.net [67.77.87.241]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id A040156055B for ; Thu, 4 Aug 2011 20:42:10 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Thu, 4 Aug 2011 16:42:01 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.4; x86_64; ; ) References: <201107101442.43605.luke@dashjr.org> <201108041629.04130.luke@dashjr.org> In-Reply-To: <201108041629.04130.luke@dashjr.org> X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201108041642.04208.luke@dashjr.org> X-Spam-Score: -0.8 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.8 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Qp4kK-00069y-7I Subject: Re: [Bitcoin-development] Useful bitcoin patches... 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, 04 Aug 2011 20:42:30 -0000 On Thursday, August 04, 2011 4:29:01 PM Luke-Jr wrote: > Jeff, you seem to have rewritten *part of* bugfix_CreateThread_leak and > neglected to attribute the original author (as my branch did/does). My apologies. BlueMatt showed me how my comment here was wrong. Hopefully I'll remember how GitHub shows merges like this in the future.