From: Drak <drak@zikula•org>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Andy Weidenbaum <archbaum@gmail•com>,
Alex Mizrahi <alex.mizrahi@gmail•com>
Subject: Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a low-level Python2/3 interface to the Bitcoin protocol
Date: Sat, 15 Mar 2014 18:04:37 +0000 [thread overview]
Message-ID: <CANAnSg0GYk3fRoj-7FZsoWGUw3+2drwaOKWC1UgywfFAgi6gGA@mail.gmail.com> (raw)
In-Reply-To: <20140315172254.GA18318@savin>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Yes. I think the problem is your fork has been under more development and
upstream has stalled. The problem with this is it becomes unclear which
repo is the main one as it really has become a fork and of course then
development really does fork properly which is a shame because it doesn't
nurture community contributions around the project which is really
important.
Drak
On 15 March 2014 17:22, Peter Todd <pete@petertodd•org> wrote:
> On Sat, Mar 15, 2014 at 05:12:42PM +0000, Drak wrote:
> > Would it make sense to pull that stuff in and add Peter with commit
> access
> > since your repo is top of the fork tree.
>
> I've noticed it looks like people actually using my 'pythonize' code
> have been linking directly to my tree in things like documentation and
> build scripts, so the URL is probably not a problem.
>
> I did open a pull-req on the bitcoin.org repo to change that URL
> however: https://github.com/bitcoin/bitcoin.org/pull/346
>
> --
> 'peter'[:-1]@petertodd.org
> 0000000000000000ef4a047ecc7077b7855626b9c9bf07e528e0c6ace2da30a8
>
[-- Attachment #2: Type: text/html, Size: 1741 bytes --]
prev parent reply other threads:[~2014-03-15 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 13:43 Peter Todd
2014-03-15 14:34 ` Peter Todd
2014-03-15 16:47 ` Jeff Garzik
2014-03-15 16:47 ` Jeff Garzik
2014-03-15 17:12 ` Drak
2014-03-15 17:21 ` Jeff Garzik
2014-03-15 17:22 ` Peter Todd
2014-03-15 18:04 ` Drak [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=CANAnSg0GYk3fRoj-7FZsoWGUw3+2drwaOKWC1UgywfFAgi6gGA@mail.gmail.com \
--to=drak@zikula$(echo .)org \
--cc=alex.mizrahi@gmail$(echo .)com \
--cc=archbaum@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)org \
/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