public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Aidan Thornton <makosoft@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.5.2 tag in github ??
Date: Fri, 3 Feb 2012 08:45:30 -0500	[thread overview]
Message-ID: <CAAS2fgQsqnUxtvfE_4f5pWBhn_ifWM2fdNvncb6_AM2YDaO=Sw@mail.gmail.com> (raw)
In-Reply-To: <CAB=c7Tp9Mu_-kux8gazysKVFHZaWZdEgsmoOVE+wz-AGYdN-XQ@mail.gmail.com>

On Fri, Feb 3, 2012 at 4:52 AM, Aidan Thornton <makosoft@gmail.com> wrote:
> I think that tag's in
> https://gitorious.org/+bitcoin-stable-developers/bitcoin/bitcoind-stable
> - a certain amount of developer politics seems to be involved, and
> v0.5.2 may not have been pushed to the official github repository.

No developer politics are involved— the cuts to the stable versions
have always been done from Luke's repository simply because he
maintains it.



      parent reply	other threads:[~2012-02-03 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  9:22 [Bitcoin-development] 0.5.2 tag in github ?? Michael Grønager
2012-02-03  9:52 ` Aidan Thornton
2012-02-03  9:59   ` Michael Grønager
2012-02-03 13:45   ` Gregory Maxwell [this message]

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='CAAS2fgQsqnUxtvfE_4f5pWBhn_ifWM2fdNvncb6_AM2YDaO=Sw@mail.gmail.com' \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=makosoft@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