public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Greg Sanders <gsanders87@gmail.com>
To: NxtChg <nxtchg@hush.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
Date: Sat, 27 Jun 2015 08:35:54 -0400	[thread overview]
Message-ID: <CAB3F3DuL11BaVG5cmJWb3BjjcDuMmm=7JPEdmDE5g8es+JKbgA@mail.gmail.com> (raw)
In-Reply-To: <20150627122558.A196641A3E@smtp.hushmail.com>

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

>That requires an assumption that all developers are perfectly representing
the whole community.

I'll take that as a "no". But it's a strange bar to set: perfect
representation of entire community. By that token, nobody can say anything
is controversial if a different group is disagreeing.

Greg

On Sat, Jun 27, 2015 at 8:25 AM, NxtChg <nxtchg@hush.com> wrote:

>
> On 6/27/2015 at 3:18 PM, "Greg Sanders" <gsanders87@gmail.com> wrote:
>
> >Can we agree n-1 dev Nacks would be a controversial hard fork?
>
> That requires an assumption that all developers are perfectly representing
> the whole community.
>
> And no shady lobbying behind the scenes too.
>
>
>

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

  reply	other threads:[~2015-06-27 12:36 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 14:09 [bitcoin-dev] The need for larger blocks Pieter Wuille
2015-06-26 14:38 ` Venzen Khaosan
2015-06-26 15:22 ` Milly Bitcoin
2015-06-26 15:24   ` Pieter Wuille
2015-06-26 18:05     ` Jeff Garzik
2015-06-26 18:32       ` Milly Bitcoin
2015-06-26 15:38 ` Tom Harding
2015-06-26 16:22   ` Venzen Khaosan
2015-06-26 17:04     ` Tom Harding
2015-06-26 17:55       ` Gavin Andresen
2015-06-26 17:57 ` Jeff Garzik
2015-06-26 18:12   ` Pieter Wuille
2015-06-26 18:23     ` Jeff Garzik
2015-06-26 18:31       ` Mark Friedenbach
2015-06-26 19:05         ` Aaron Voisine
2015-06-26 18:34       ` Pieter Wuille
2015-06-26 19:18         ` Ross Nicoll
2015-06-26 19:36           ` Peter Todd
2015-06-27  6:13             ` Filipe Farinha
2015-06-27  7:14               ` Aaron Voisine
2015-06-27 15:13                 ` Peter Todd
2015-06-27 19:40                   ` Aaron Voisine
2015-06-26 18:47       ` Patrick Strateman
2015-06-26 19:03         ` Tier Nolan
2015-06-26 19:12           ` Mark Friedenbach
2015-06-26 20:44       ` Owen Gunden
2015-06-27  2:18         ` Eric Lombrozo
2015-06-27  2:54           ` Eric Lombrozo
2015-06-27  8:16           ` Venzen Khaosan
2015-06-26 18:29     ` Alex Morcos
2015-06-27  7:43 ` Wladimir J. van der Laan
2015-06-27  9:55   ` NxtChg
2015-06-27 10:04     ` Wladimir J. van der Laan
2015-06-27 10:29       ` NxtChg
2015-06-27 11:04         ` Jorge Timón
2015-06-27 11:18           ` Eric Lombrozo
2015-06-27 11:43             ` Jorge Timón
2015-06-27 12:10           ` NxtChg
2015-06-28 12:13             ` Jorge Timón
2015-06-28 13:51               ` Ivan Brightly
2015-06-28 14:13                 ` Eric Lombrozo
2015-06-28 14:16                 ` Eric Lombrozo
2015-06-28 14:22                   ` Ivan Brightly
2015-06-28 15:05                 ` Jorge Timón
2015-06-28 16:01                   ` Ivan Brightly
2015-06-28 15:28               ` s7r
2015-06-28 15:45                 ` Jorge Timón
2015-06-27 10:19     ` Venzen Khaosan
2015-06-27 19:55       ` Aaron Voisine
2015-06-28 16:37         ` Venzen Khaosan
2015-06-28 20:56           ` Aaron Voisine
2015-06-27 10:13   ` Jorge Timón
2015-06-27 12:09     ` Wladimir J. van der Laan
2015-06-27 12:15       ` NxtChg
2015-06-27 12:17         ` Greg Sanders
2015-06-27 12:25           ` NxtChg
2015-06-27 12:35             ` Greg Sanders [this message]
2015-06-27 12:25         ` Wladimir J. van der Laan
2015-06-27 12:50           ` NxtChg
2015-06-27 13:01             ` Wladimir J. van der Laan
2015-06-28 12:03       ` Jorge Timón

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='CAB3F3DuL11BaVG5cmJWb3BjjcDuMmm=7JPEdmDE5g8es+JKbgA@mail.gmail.com' \
    --to=gsanders87@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=nxtchg@hush.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