From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place
Date: Mon, 18 Jun 2012 13:25:21 +0000 [thread overview]
Message-ID: <201206181325.23041.luke@dashjr.org> (raw)
In-Reply-To: <CAD2Ti29_NcLyfEB3b=Xur=Q37SP6Cn34b5ZzOTmucLdni3of=w@mail.gmail.com>
On Monday, June 18, 2012 8:09:56 AM grarpamp wrote:
> > I guess I've been neglecting to update the stable repo with
> > releases tagged in master. It should be fixed now.
>
> Yes, that has helped! Now git'ers can easily compare the release
> tags to stable 'x' branches on gitorious. I don't know how to do
> that across repos yet, save manuel diff of checkouts from each,
> which would have been required prior to this update you made.
This is the work model I use:
git clone git://github.com/bitcoin/bitcoin.git
cd bitcoin
git remote add stable git://gitorious.org/+bitcoin-stable-developers/bitcoin/bitcoind-stable.git
git remote add personal git@github•com:YOURNAME/bitcoin.git
With this, you can use "git fetch --all" to update your copy of the remote
branches, and access them as "origin/master", "stable/0.6.x", etc; and push
personal branches using "git push personal <branch>"
Luke
next prev parent reply other threads:[~2012-06-18 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 9:22 grarpamp
2012-06-17 10:17 ` Gregory Maxwell
2012-06-17 21:35 ` grarpamp
2012-06-17 21:52 ` Gregory Maxwell
2012-06-17 23:04 ` grarpamp
2012-06-18 0:02 ` Luke-Jr
2012-06-18 3:27 ` grarpamp
2012-06-18 3:57 ` Luke-Jr
2012-06-18 8:09 ` grarpamp
2012-06-18 13:25 ` Luke-Jr [this message]
2012-06-20 9:06 ` grarpamp
2012-06-18 0:07 ` Gregory Maxwell
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=201206181325.23041.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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