From: Gregory Maxwell <gmaxwell@gmail.com>
To: Paul Rabahy <prabahy@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Reconsidering github
Date: Sat, 23 Aug 2014 13:54:08 -0700 [thread overview]
Message-ID: <CAAS2fgTQtf75CRFeVW0przyKwMk9VEdFSQJ656WifauOxaNP6g@mail.gmail.com> (raw)
In-Reply-To: <CADu7o8Nc4iZFoSY4AtVEQhiL5JhS34hJS+QTkNrnX9U4ATZWZQ@mail.gmail.com>
On Sat, Aug 23, 2014 at 1:36 PM, Paul Rabahy <prabahy@gmail.com> wrote:
> I want go give a bit of an outsiders perspective. I thoroughly understand
> the concepts of bitcoin and am a professional programmer, but have never
> taken the time to compile my own copy of bitcoin core.
>
> I have looked at the pull requests on Github many times. I have cloned the
> repo to my own computer, but haven't really used that to do much. I find
> Github very easy to use, and (to me) it has the lowest bar to get more eyes
> passively looking at the code. As a security guy, I appreciate the extra
> time and effort that goes into signing commits and merges even if I have not
> personally verified the signatures. I would like to see bitcoin core
> continue to use github, but have no objection to additional mirrors of the
> repo being hosted on different sites.
Nothing suggested here would ever remove the ability to go and explore
and read the changes just as you're doing so.
Already the way it works is that our local repositories are
authoritative for each of us. (Git itself is a decentralized system
regardless of github's efforts to make it look otherwise).
next prev parent reply other threads:[~2014-08-23 20:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 12:02 [Bitcoin-development] Reconsidering github Jeff Garzik
2014-08-19 12:28 ` Dāvis Mosāns
2014-08-19 14:58 ` Wladimir
2014-08-20 1:26 ` Troy Benjegerdes
2014-08-20 1:34 ` Gregory Maxwell
2014-08-20 6:24 ` Wladimir
2014-08-20 14:16 ` Mike Hearn
2014-08-23 5:59 ` Troy Benjegerdes
2014-08-23 5:53 ` Troy Benjegerdes
2014-08-30 3:33 ` Odinn Cyberguerrilla
2014-08-19 15:44 ` Bryan Bishop
2014-08-19 17:04 ` Angel Leon
2014-08-19 18:54 ` Gregory Maxwell
2014-08-22 19:20 ` xor
2014-08-22 19:31 ` Angel Leon
2014-08-23 6:17 ` Troy Benjegerdes
2014-08-23 11:38 ` Pieter Wuille
2014-08-23 12:05 ` Drak
2014-08-23 15:56 ` Wladimir
2014-08-23 11:59 ` Angel Leon
2014-08-23 14:32 ` Peter Todd
2014-08-23 17:44 ` Troy Benjegerdes
2014-08-23 20:36 ` Paul Rabahy
2014-08-23 20:54 ` Gregory Maxwell [this message]
2014-08-23 22:45 ` Peter Todd
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=CAAS2fgTQtf75CRFeVW0przyKwMk9VEdFSQJ656WifauOxaNP6g@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=prabahy@gmail.com \
/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