diff options
| author | Gregory Maxwell <gmaxwell@gmail.com> | 2014-08-19 11:54:38 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-08-19 18:54:44 +0000 |
| commit | 129987d9350ddfa6a90543653fcd08144eca5b10 (patch) | |
| tree | 6f83679626d51fb046901778d332ac92af257e4b | |
| parent | ec5a619b567e7bf551731e821e3d5ea7930dfc5d (diff) | |
| download | pi-bitcoindev-129987d9350ddfa6a90543653fcd08144eca5b10.tar.gz pi-bitcoindev-129987d9350ddfa6a90543653fcd08144eca5b10.zip | |
Re: [Bitcoin-development] Reconsidering github
| -rw-r--r-- | 66/329baebbf94ae20ba6598290ec63eff99853d5 | 75 |
1 files changed, 75 insertions, 0 deletions
diff --git a/66/329baebbf94ae20ba6598290ec63eff99853d5 b/66/329baebbf94ae20ba6598290ec63eff99853d5 new file mode 100644 index 000000000..dbde89baf --- /dev/null +++ b/66/329baebbf94ae20ba6598290ec63eff99853d5 @@ -0,0 +1,75 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <gmaxwell@gmail.com>) id 1XJoYO-0007Rn-Ub + for bitcoin-development@lists.sourceforge.net; + Tue, 19 Aug 2014 18:54:44 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.213.180 as permitted sender) + client-ip=209.85.213.180; envelope-from=gmaxwell@gmail.com; + helo=mail-ig0-f180.google.com; +Received: from mail-ig0-f180.google.com ([209.85.213.180]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1XJoYN-0005jM-Um + for bitcoin-development@lists.sourceforge.net; + Tue, 19 Aug 2014 18:54:44 +0000 +Received: by mail-ig0-f180.google.com with SMTP id l13so10139078iga.7 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 19 Aug 2014 11:54:38 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.50.80.39 with SMTP id o7mr23108422igx.0.1408474478595; Tue, + 19 Aug 2014 11:54:38 -0700 (PDT) +Received: by 10.107.14.67 with HTTP; Tue, 19 Aug 2014 11:54:38 -0700 (PDT) +In-Reply-To: <CAJHLa0NXAYh9HzazN6gArUV8y7J8_G0oqkZqPBgibpW0wRNxKQ@mail.gmail.com> +References: <CAJHLa0NXAYh9HzazN6gArUV8y7J8_G0oqkZqPBgibpW0wRNxKQ@mail.gmail.com> +Date: Tue, 19 Aug 2014 11:54:38 -0700 +Message-ID: <CAAS2fgSpWWH5UkeQewtebjuhpT=S=gR36KzuSCoYb-Vw3MdNPg@mail.gmail.com> +From: Gregory Maxwell <gmaxwell@gmail.com> +To: Jeff Garzik <jgarzik@bitpay.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 + (gmaxwell[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: 1XJoYN-0005jM-Um +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Reconsidering github +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: Tue, 19 Aug 2014 18:54:45 -0000 + +On Tue, Aug 19, 2014 at 5:02 AM, Jeff Garzik <jgarzik@bitpay.com> wrote: +> It would be nice if the issues and git repo for Bitcoin Core were not +> on such a centralized service as github, nice and convenient as it is. +> +> To that end, I note that Linux does its own git repo, and now requires +> 2FA: http://www.linux.com/news/featured-blogs/203-konstantin-ryabitsev/784544-linux-kernel-git-repositories-add-2-factor-authentication +> +> As a first step, one possibility is putting the primary repo on +> bitcoin.org somewhere, and simply mirroring that to github for each +> push. + +The obvious thing to do is setup the second repository and get it +going. Git doesn't really care all that much whats "primary". If we +have a working workflow elsewhere then making a change won't be a leap +of faith. + + |