From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place
Date: Mon, 18 Jun 2012 04:09:56 -0400 [thread overview]
Message-ID: <CAD2Ti29_NcLyfEB3b=Xur=Q37SP6Cn34b5ZzOTmucLdni3of=w@mail.gmail.com> (raw)
In-Reply-To: <201206180357.13430.luke@dashjr.org>
> Workflow is ...
Thanks very much, I think that helps me/others. I did not realize
there were release windows in master and thought it more as the
typical full time dev slush. That also explains the presence of all
the release tags in github repo. And even, in a divergent way, the
presence of github/0.6.2 as path to gitorius/0.6.x. And I agree
with the (last bugfix after release) -> import/maintain model, it
would be similar in solo repo.
> 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.
Also, these declarations of defunctness help sort out too.
# git branch -vv -a
"This stable branch is no longer maintained."
Ok, so for my works I will now track github/master (edge) and
gitorious/0.bigN(eg: 6).x (stable) against gitorious/bigTagRelease
(latest public). Thanks guys, and Luke :)
I hope other with similar questions find this thread. Apology for
subverting its subject somehows.
next prev parent reply other threads:[~2012-06-18 8:10 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 [this message]
2012-06-18 13:25 ` Luke-Jr
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='CAD2Ti29_NcLyfEB3b=Xur=Q37SP6Cn34b5ZzOTmucLdni3of=w@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