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 <laanwj@gmail.com>) id 1Wgpu9-0004JS-8Z for bitcoin-development@lists.sourceforge.net; Sun, 04 May 2014 06:28:05 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.174 as permitted sender) client-ip=209.85.213.174; envelope-from=laanwj@gmail.com; helo=mail-ig0-f174.google.com; Received: from mail-ig0-f174.google.com ([209.85.213.174]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wgpu8-0001cP-Di for bitcoin-development@lists.sourceforge.net; Sun, 04 May 2014 06:28:05 +0000 Received: by mail-ig0-f174.google.com with SMTP id h3so214290igd.13 for <bitcoin-development@lists.sourceforge.net>; Sat, 03 May 2014 23:27:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.85.18 with SMTP id d18mr15246388igz.42.1399184878482; Sat, 03 May 2014 23:27:58 -0700 (PDT) Received: by 10.64.22.168 with HTTP; Sat, 3 May 2014 23:27:58 -0700 (PDT) In-Reply-To: <CACq0ZD7SP==2cMCHnYPiHwh-MWwuWCKVX5T8+3P7xMAG+5i91g@mail.gmail.com> References: <CACq0ZD6EJnG4iwehfcFU-4AhBiNdtyf7eE9iGW8d6rv6327Eug@mail.gmail.com> <53644F13.1080203@gmail.com> <CACq0ZD7s8tp8GvJhEhZx4T7xMpeZ+tz5HNKQK-p=f=R10NaCmA@mail.gmail.com> <CANOOu=9orMZH6fpTfkO8zgwPDmwpA8WW78EKwSTiw2GXn7UCxA@mail.gmail.com> <A4150064-81C5-4B39-B696-B4F778531F3B@swipeclock.com> <53659234.3020207@gmail.com> <CANAnSg1=ap03K-Rxhje0RP-nxt8eWzWiURzXrMBe3Au-bBUBpQ@mail.gmail.com> <CACq0ZD7SP==2cMCHnYPiHwh-MWwuWCKVX5T8+3P7xMAG+5i91g@mail.gmail.com> Date: Sun, 4 May 2014 08:27:58 +0200 Message-ID: <CA+s+GJAgYOmQ8GkJU5r3NZTHraq51e+z8EFyQkE=Kk7cP5dcoA@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: Aaron Voisine <voisine@gmail.com> Content-Type: text/plain; charset=UTF-8 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 (laanwj[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: 1Wgpu8-0001cP-Di Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] "bits": Unit of account 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: Sun, 04 May 2014 06:28:05 -0000 On Sun, May 4, 2014 at 8:15 AM, Aaron Voisine <voisine@gmail.com> wrote: > Bit by bit, it's become clear that it's a bit much to worry even a > little bit that overloading the word "bit" would be every bit as bad > as a two bit horse with the bit between it's teeth that bit the hand > that feeds it, or a drill bit broken to bits after just a bit of use. +1 good summary And I think that's a good conclusion to this discussion about unit names on the development mailing list. Everything has been said now. Wladimir