public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Btc Drak <btcdrak@gmail.com>
To: Gary Mulder <flyingkiwiguy@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin-dev list etiquette
Date: Wed, 19 Aug 2015 23:59:07 +0100	[thread overview]
Message-ID: <CADJgMztTAKL3NODCGcW+qsHqZreJyg3tD8VBPRAnYhcftS9UtA@mail.gmail.com> (raw)
In-Reply-To: <CAKy9zTCjSDLo3c2bzCD1rwX_RKVzzvP47AH5_EL3v5VHNZ9vZQ@mail.gmail.com>

On Wed, Aug 19, 2015 at 11:25 PM, Gary Mulder via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> So guys, do we need a BIP to address the existence of XT and its possible
> impact to the block chain?

I believe there is BIP99 that addresses hard forks.


  reply	other threads:[~2015-08-19 22:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 20:08 [bitcoin-dev] bitcoin-dev list etiquette Alex Morcos
2015-08-19 20:11 ` Eric Lombrozo
2015-08-19 20:19   ` Eric Lombrozo
2015-08-19 21:19     ` Hector Chu
2015-08-19 21:51       ` Theo Chino
2015-08-19 21:54         ` Nelson Castillo
2015-08-19 22:12           ` Theo Chino
2015-08-19 22:25             ` Gary Mulder
2015-08-19 22:59               ` Btc Drak [this message]
2015-08-19 23:13               ` 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=CADJgMztTAKL3NODCGcW+qsHqZreJyg3tD8VBPRAnYhcftS9UtA@mail.gmail.com \
    --to=btcdrak@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=flyingkiwiguy@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