public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gary Rowe <g.rowe@froot.co.uk>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
Date: Thu, 2 Feb 2012 17:46:11 +0000	[thread overview]
Message-ID: <CAKm8k+1CnDbSi-qfOZBCcS=H2zh5bP4RX6jgRv5H4005e5kveA@mail.gmail.com> (raw)
In-Reply-To: <1328204347.3023.0.camel@BMThinkPad.lan.bluematt.me>

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

OK - I've added a comment to the pull request.

On 2 February 2012 17:39, Matt Corallo <bitcoin-list@bluematt.me> wrote:

> Not yet, its up to genjix (Amir) to do that.  See
> https://github.com/genjix/bips/pull/2
>
> Matt
>
> On Thu, 2012-02-02 at 17:07 +0000, Gary Rowe wrote:
> > BlueMatt, did the BIP0021 Wiki entry for "req:" to "req-" get updated?
> > I'm looking there now and it seems to be still at "req:"
> >
> ------------------------------------------------------------------------------
> > Keep Your Developer Skills Current with LearnDevNow!
> > The most comprehensive online learning library for Microsoft developers
> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> > Metro Style Apps, more. Free future releases when you subscribe now!
> > http://p.sf.net/sfu/learndevnow-d2d
> > _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

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

  reply	other threads:[~2012-02-02 17:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 17:07 [Bitcoin-development] BIP 20 Rejected, process for BIP 21N Gary Rowe
2012-02-02 17:39 ` Matt Corallo
2012-02-02 17:46   ` Gary Rowe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-31 14:27 Amir Taaki
2012-01-31 14:33 ` slush
2012-01-31 14:52   ` Amir Taaki
     [not found]   ` <CAKm8k+1cHagzj3T27S=h0PueH8EgcCkEajZGgAw7HcQ=N-46ow@mail.gmail.com>
2012-01-31 14:53     ` Gary Rowe
2012-01-31 15:02       ` Gregory Maxwell
2012-01-31 15:04         ` Gary Rowe
2012-01-31 14:59   ` Gregory Maxwell
2012-01-31 16:04 ` Matt Corallo
2012-01-31 18:22   ` Matt Corallo
2012-01-31 19:02     ` Wladimir
2012-01-31 21:42       ` Matt Corallo
2012-01-31 22:14     ` Andreas Schildbach
2012-01-31 22:37       ` Gary Rowe
2012-01-31 22:47         ` Matt Corallo
2012-02-04 14:03     ` thomasV1
2012-02-04 16:03       ` Gary Rowe
2012-02-04 17:15         ` Matt Corallo
2012-01-31 16:07 ` Luke-Jr

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='CAKm8k+1CnDbSi-qfOZBCcS=H2zh5bP4RX6jgRv5H4005e5kveA@mail.gmail.com' \
    --to=g.rowe@froot.co.uk \
    --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