From: Christian Decker <decker.christian@gmail•com>
To: Stefan Thomas <moon@justmoon•de>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [RFC] BIP 14 - Protocol Version and User Agent
Date: Mon, 14 Nov 2011 13:09:23 +0100 [thread overview]
Message-ID: <CALxbBHVS+m1evgkGEwdEYAjBwze3npKFfdhmfFW0eegoPeLzsg@mail.gmail.com> (raw)
In-Reply-To: <4EC0D5F8.40506@justmoon.de>
[-- Attachment #1: Type: text/plain, Size: 3225 bytes --]
Same here of course, but I'll keep the String short and fixed. I still
don't think there should be any reason for others to know my OS in order to
communicate with me :-)
On Mon, Nov 14, 2011 at 9:48 AM, Stefan Thomas <moon@justmoon•de> wrote:
> Nice. I'll check with justmoon when I hopefully meet him at the
> conference.
>
>
> It's all fine with me. As soon as the original client switches to the new
> format, we will, too.
>
>
>
>
> On 11/13/2011 09:52 PM, Amir Taaki wrote:
>
> Nice. I'll check with justmoon when I hopefully meet him at the
> conference. If all is OK, hopefully 0.6 will be the last protocol version
> bump for a while.
>
> ------------------------------
> *From:* Mike Hearn <mike@plan99•net> <mike@plan99•net>
> *To:* Amir Taaki <zgenjix@yahoo•com> <zgenjix@yahoo•com>
> *Cc:* "bitcoin-development@lists.sourceforge.net"<bitcoin-development@lists•sourceforge.net>
> <bitcoin-development@lists.sourceforge.net><bitcoin-development@lists•sourceforge.net>
> *Sent:* Saturday, November 12, 2011 7:31 PM
> *Subject:* Re: [Bitcoin-development] [RFC] BIP 14 - Protocol Version and
> User Agent
>
> Looks pretty reasonable to me. If Gavin changes the mainline client to use
> this format I'll change BitcoinJ as well. It'll need a bit of API work so
> clients are sure to set it up properly.
>
> On Thu, Nov 10, 2011 at 10:16 PM, Amir Taaki <zgenjix@yahoo•com> wrote:
>
> Hi,
>
> https://en.bitcoin.it/wiki/BIP_0014
>
> Thanks to Gavin Andresen for proof reading and suggesting
> clarifications. Thanks to Patrick Strateman for suggesting the hierarchical
> format and pointing out some flaws of browser user-agents to me.
>
> The timeline is written in the past tense since BIPs are meant to be
> readable in the future for explaining why we took certain decisions with
> bitcoin. A nice cache for future historians when bitcoin is ubiquitous ;)
>
> The next version 0.6 should be the protocol version which becomes peeled
> off from the current client. There are still some changes migrating into
> the protocol that need to be finished.
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register nowhttp://p.sf.net/sfu/rsa-sfdev2dev1
>
>
>
> _______________________________________________
> Bitcoin-development mailing listBitcoin-development@lists•sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 7498 bytes --]
prev parent reply other threads:[~2011-11-14 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 21:16 Amir Taaki
2011-11-12 19:31 ` Mike Hearn
2011-11-13 20:52 ` Amir Taaki
2011-11-14 8:48 ` Stefan Thomas
2011-11-14 12:09 ` Christian Decker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALxbBHVS+m1evgkGEwdEYAjBwze3npKFfdhmfFW0eegoPeLzsg@mail.gmail.com \
--to=decker.christian@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=moon@justmoon$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox