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 <jgarzik@bitpay.com>) id 1WOBSn-0004Xa-Sp for bitcoin-development@lists.sourceforge.net; Thu, 13 Mar 2014 19:38:45 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.170 as permitted sender) client-ip=209.85.212.170; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f170.google.com; Received: from mail-wi0-f170.google.com ([209.85.212.170]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WOBSm-0006XN-UP for bitcoin-development@lists.sourceforge.net; Thu, 13 Mar 2014 19:38:45 +0000 Received: by mail-wi0-f170.google.com with SMTP id n15so4019871wiw.5 for <bitcoin-development@lists.sourceforge.net>; Thu, 13 Mar 2014 12:38:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=AUZfB9U0/vTturETj2Oa35sdOpQ5XYT//MGlYq/Xexc=; b=OAUFfpUy6XjSlatlRHW5QZt14MZ1N06JKyUGptbKOokTmL89qG/GvcjAi6nHy88ns9 BHo/VoAi/FeMnzHKwHN6S881myJuWS269j2OIIpC841jFeFOeunrrK5SFFnGpTT+IXpv 42g03SOvSbEpUqRTxE7EEslqISGA3Mqas9WVbQ8irhS8Izg6ITnj0OGzhmgDpXx223o4 MGahptD82hV/Bb7EBrdhbIP1gjepAWdlvfCgM62iIc8dkoYBw5WahQi6OyFASr5g8ndR iUAgDk7UAMAOqV63ILReLp8fOSn6kbYNPVo9Vn4XKCNnLgU/pV5XT2TW3oGLuY/mQRNm aMrQ== X-Gm-Message-State: ALoCoQksyF/H6NZOMsrpQkFvYyZMzpiIUTs4lrfDgXm88g+/GBYrSrZBIdZkNkVgXZrChCK0W4L3 X-Received: by 10.180.97.37 with SMTP id dx5mr2942394wib.53.1394739518278; Thu, 13 Mar 2014 12:38:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Thu, 13 Mar 2014 12:38:17 -0700 (PDT) In-Reply-To: <CANEZrP1VbQPapKJCLcE0+vpK0xac6D6JxRGKdagPVchfZjpUmQ@mail.gmail.com> References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com> <52852C2D.9020103@gmail.com> <52853D8A.6010501@monetize.io> <CAJHLa0M6CkoDbD6FFixf9-mmhug7DvehSWCJ+EHWVxUDuwNiBg@mail.gmail.com> <EE02A310-8604-4811-B2D0-FC32C72C20F3@grabhive.com> <CAJHLa0OMcTCgGESi-F4jT2NA3FyCeMYbD_52j47t3keEYBfK8g@mail.gmail.com> <CAKm8k+3J9Po4xQn9LhTQrnrGCvG36-kLCjWPX4kmd-c7h+LujA@mail.gmail.com> <CANEZrP1VbQPapKJCLcE0+vpK0xac6D6JxRGKdagPVchfZjpUmQ@mail.gmail.com> From: Jeff Garzik <jgarzik@bitpay.com> Date: Thu, 13 Mar 2014 15:38:17 -0400 Message-ID: <CAJHLa0PsB6BtYSfN=X1En5iyyfJh5MnuLQgh-6O+6+dO78d29w@mail.gmail.com> To: Mike Hearn <mike@plan99.net> Content-Type: text/plain; charset=ISO-8859-1 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 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: 1WOBSm-0006XN-UP Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>, Gary Rowe <g.rowe@froot.co.uk> Subject: Re: [Bitcoin-development] moving the default display to mbtc 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: Thu, 13 Mar 2014 19:38:46 -0000 On Thu, Mar 13, 2014 at 9:31 AM, Mike Hearn <mike@plan99.net> wrote: > The standard has become mBTC and that's what was adopted. It's too late to > try and sway this on a mailing list thread now. Just saying that doesn't make it so, nor does it make it a good idea. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/