public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: JMOlmos GMail <colonizare@gmail.com>
To: Isidor Zeuner <cryptocurrencies@quidecco.de>,
	bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
Date: Mon, 7 Jul 2014 14:57:46 -0300	[thread overview]
Message-ID: <CANVdSAp_1wBYuh2+hcR_HCtOjmwDm8EJdWLdJ4ZWcd5PARVW6A@mail.gmail.com> (raw)
In-Reply-To: <CANVdSAqEyqavSHea3uhzVWGKQU0UHGZDVqEiF3Ox2XkhwM=zpA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]

And for translation's facility :P


2014-07-07 14:57 GMT-03:00 JMOlmos GMail <colonizare@gmail.com>:

> And for translation's facility :P
>
>
> 2014-07-02 22:21 GMT-03:00 Isidor Zeuner <cryptocurrencies@quidecco.de>:
>
> Hello Krzysztof,
>>
>> [...]
>> > As before, it can be found under:
>> >
>> > http://enetium.com/resources/Bitcoin.pdf
>> >
>> > I hope it will prove useful to the community and thank in advance
>> > for any further improvement proposals.
>> >
>>
>> I think it's great work and provides a good reference for those
>> who want to get some insight into Bitcoin's design.
>>
>> Have you considered putting the document source under version control,
>> which may facilitate tracking future protocol improvements in the
>> document easily?
>>
>> Best regards,
>>
>> Isidor
>>
>>
>> ------------------------------------------------------------------------------
>> Open source business process management suite built on Java and Eclipse
>> Turn processes into business applications with Bonita BPM Community
>> Edition
>> Quickly connect people, data, and systems into organized workflows
>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>> http://p.sf.net/sfu/Bonitasoft
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2535 bytes --]

  parent reply	other threads:[~2014-07-07 17:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 11:30 [Bitcoin-development] Bitcoin Protocol Specification Krzysztof Okupski
2014-07-03  1:21 ` Isidor Zeuner
     [not found]   ` <CANVdSAqEyqavSHea3uhzVWGKQU0UHGZDVqEiF3Ox2XkhwM=zpA@mail.gmail.com>
2014-07-07 17:57     ` JMOlmos GMail [this message]
2014-07-08 15:29       ` Chris D'Costa
2014-07-08 20:04         ` Matt Whitlock
2014-07-08 21:08           ` Aaron Voisine
2014-07-08 22:40           ` Jorge Timón
2014-07-09 11:57           ` Mike Hearn
  -- strict thread matches above, loose matches on Subject: below --
2014-07-14 14:44 Krzysztof Okupski
2014-07-14 17:16 ` Jeff Garzik
2014-07-14  9:54 Krzysztof Okupski
2014-07-14 10:41 ` sickpig
2014-07-14 11:26 ` Mike Hearn
2014-07-14 11:41   ` Wladimir
2014-07-14 11:49     ` Mike Hearn
2014-07-14 12:25   ` sickpig
2014-07-14 12:37     ` Mike Hearn
2014-07-14 20:51       ` sickpig
2014-07-09  9:34 Krzysztof Okupski
2014-05-18 13:35 Krzysztof Okupski
2014-05-18 14:38 ` Adam Back

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=CANVdSAp_1wBYuh2+hcR_HCtOjmwDm8EJdWLdJ4ZWcd5PARVW6A@mail.gmail.com \
    --to=colonizare@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=cryptocurrencies@quidecco.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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