From: grarpamp <grarpamp@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Git repo choices
Date: Sun, 19 Feb 2012 17:00:22 -0500 [thread overview]
Message-ID: <CAD2Ti2-0nMARZ-vyDk0-ToKF-SvHMrG65Pe9Bwv6TLkfwmEqew@mail.gmail.com> (raw)
I'm a little unclear on which repo is which and
for what intended uses. And other than #1,
their descriptions on the hubs are minimal.
I'm not the best with git, but getting there.
Are these the right way to think of them?
And that #1 and #3 are what most builders
and hacks should be tracking?
#1
https://github.com/bitcoin/bitcoin.git
The current development tree. As such, HEAD/master/origin
may at times not be exactly reliable/usable.
#2
https://git.gitorious.org/bitcoin/bitcoind.git
A copy of some chunk of #1 that then died
off around v0.4.0. Purposed similar to #3?
#3
https://git.gitorious.org/bitcoin/bitcoind-stable.git
Another copy of #1. For development along stable
branches and making release cuts from same?
Releases get pulled back to #1 for keeping?
The HEAD/master/origin should be reliable.
Why is this functoin not a part of #1?
Thanks.
reply other threads:[~2012-02-19 22:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAD2Ti2-0nMARZ-vyDk0-ToKF-SvHMrG65Pe9Bwv6TLkfwmEqew@mail.gmail.com \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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