public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: coinscoins <danteat7@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] is there a way to do bitcoin-staging?
Date: Thu, 21 Nov 2013 20:22:33 +0000 (UTC)	[thread overview]
Message-ID: <loom.20131121T212121-510@post.gmane.org> (raw)
In-Reply-To: 20131014180807.GA32082@netbook.cypherspace.org

looks like Betacoin is already here - http://betacoin.org




  parent reply	other threads:[~2013-11-21 20:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 13:23 [Bitcoin-development] is there a way to do bitcoin-staging? Adam Back
2013-05-19 15:08 ` Peter Vessenes
2013-05-20  6:34   ` Alan Reiner
2013-10-14 18:08     ` Adam Back
2013-10-14 18:21       ` Jeff Garzik
2013-11-21 20:22       ` coinscoins [this message]
2013-11-21 20:35       ` Melvin Carvalho
2013-11-21 21:11         ` [Bitcoin-development] bitcoin 1.x & 0.x in parallel (Re: is there a way to do bitcoin-staging?) Adam Back
2014-03-16 22:58       ` [Bitcoin-development] 2-way pegging " Adam Back
2014-03-16 23:22         ` Jorge Timón
2014-03-17 15:55         ` Gregory Maxwell
2013-10-14 18:43     ` [Bitcoin-development] is there a way to do bitcoin-staging? Michael Gronager
2013-10-14 20:20       ` Alan Reiner
2013-05-22  3:37   ` zooko
2013-05-22  4:12     ` Jeff Garzik
2013-05-20  7:12 ` Luke-Jr
2013-06-13 13:39 ` Adam Back
2013-06-14 19:20   ` Peter Todd
2013-06-14 20:50     ` Adam Back
2013-06-14 21:10       ` Luke-Jr
2013-06-14 21:25         ` Andreas Petersson
2013-06-15  0:09           ` Dennison Bertram
2013-06-15  1:57             ` Luke-Jr
2013-06-15  8:43               ` Dennison Bertram
2013-06-15 11:18 ` Melvin Carvalho
2013-06-15 13:26   ` Dennison Bertram
2013-06-16 15:46     ` Dennison Bertram

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=loom.20131121T212121-510@post.gmane.org \
    --to=danteat7@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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