summaryrefslogtreecommitdiff
path: root/03/3c66f33ca59a3e3aafef037ecd69bfa84e655c
blob: e01c58bb0d5104ed304ccd6b3a8324e7f6fbd51c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1SoKpI-0007us-M5
	for bitcoin-development@lists.sourceforge.net;
	Mon, 09 Jul 2012 20:45:00 +0000
X-ACL-Warn: 
Received: from mail-lb0-f175.google.com ([209.85.217.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SoKpF-0003jN-Ld
	for bitcoin-development@lists.sourceforge.net;
	Mon, 09 Jul 2012 20:45:00 +0000
Received: by lbol5 with SMTP id l5so17826261lbo.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 09 Jul 2012 13:44:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type:x-gm-message-state;
	bh=hrHZ0AI7U1F8pjv4uKPIzJiz9e/RM0RpsZgu4cfweB4=;
	b=l/jF2sKC6i24ud9D23a62+ZNZCxmzuQaV1xoEkT43dgLhItm7VJBlsjxjW1pQYCQ3a
	ByAA/qIo+F++un50soqPqeGt2dLI1p5cTpiZsD9lwNHEj4tBXEQhT+jqIa89AWFABTsw
	Q7nI6IjFrLSkoe66BPYhMCxoegR+QUMmxJB7Sr/G9mrqUY529h1BI5sfqQH3eyIPLImw
	+57SdiVu0manLOxOnt8F34/yomup50lMOy87eY4/gpkDRgbT1Vsh7ob1P5+D8p1LFslB
	7twSdsZ1tD2HUMPcdmPOY+5RPIOsRPAAcS6Af2/PuBgW8ZWfk01dAd1u1Q2MR9I799Yg
	sqWA==
MIME-Version: 1.0
Received: by 10.112.49.230 with SMTP id x6mr19313120lbn.86.1341866691004; Mon,
	09 Jul 2012 13:44:51 -0700 (PDT)
Received: by 10.114.63.165 with HTTP; Mon, 9 Jul 2012 13:44:50 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <CAAS2fgRd0gqrxXs4Le6nydYBaG7EO=T7FrtX6QZpg3aJtAxSvg@mail.gmail.com>
References: <1341849295.94710.YahooMailNeo@web121003.mail.ne1.yahoo.com>
	<CAAS2fgRd0gqrxXs4Le6nydYBaG7EO=T7FrtX6QZpg3aJtAxSvg@mail.gmail.com>
Date: Mon, 9 Jul 2012 16:44:50 -0400
Message-ID: <CA+8xBpcXe8evJpmJOMGjhrBNkcThu6A9uUiCjg0uqr+JokQjhw@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmlmXz4ggwg79rRM3P5eDkydlp43iQSybyXyOsdltWtKIgT2V9aIE6WNyYw+bWKArVtn/ep
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1SoKpF-0003jN-Ld
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Random order for clients page
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: Mon, 09 Jul 2012 20:45:00 -0000

On Mon, Jul 9, 2012 at 12:04 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> If you had authored this as a pull request rather than making the
> change unilaterally I would have recommended leaving it so the
> reference client was always first. I also would have suggested that it
> use JS randomization instead of jekyll in order to get more even
> coverage, though I think thats a more minor point.

Agreed, and this would be why I support revert -- pull requests are
for anything non-trivial.  This practice of pull requests clearly
should be followed in the case of controversial changes.

> Some people were concerned when this page was created that it would
> just be a source of useless disputes.  I think its becoming clear that
> this is the case. I think the cost of dealing with this page is
> starting to exceed the benefit it provides and we should probably
> consider removing it.

Agreed.
-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com