* [sup-talk] sup news (including 0.6 release)
@ 2008-07-31 2:10 William Morgan
2008-07-31 2:22 ` John Bent
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: William Morgan @ 2008-07-31 2:10 UTC (permalink / raw)
Hi all,
Some news:
- I've moved Sup over to Gitorious. I don't know that this will
magically spur a continuous stream of bugfixes, but at least now we
have a repo webpage that's not broken.
If you're running from Git, you should update your repo to pull from
there.
If you don't have local changes, you can simply reclone it:
git clone git://gitorious.org/sup/mainline.git
If you want to preserve your local repository, you can do something like:
git remote add gitorious git://gitorious.org/sup/mainline.git
git fetch
Then for each branch that you want "git pull" to pull from gitorious,
you'll need to do:
git config branch.<branch>.remote gitorious
git config branch.<branch>.merge refs/heads/<branch>
and then check it out and try pulling. If you haven't made any
commits, this should be a fast-forward.
If you want to call the remote "origin" instead of "gitorious", you'll
just have to remove or rename your origin remote first. The commands
above will be the same.
Note that I've reset the "next" branch, so if you have commits on that
branch, life may be little more complicated. Doing the above and merging
should work. Or you can isolate your changes somehow and rebase
--onto, if you feel like being complicated.
- I've merged all outstanding topic branches down to master, and
cherry-picked a couple commits that somehow ended up in next by
themselves. So master should be the latest and greatest for the
moment.
- I've moved the bugs dir directly into master. The bugs branch is now
deprecated. (It doesn't even exist in the Gitorious repo.)
- I'm planning on release an 0.6 soon with all the bugfixes we have so
far. To this end, I've unassigned all unclosed issues from the 0.6
release.
- Can anyone confirm that that the master branch on gitorious works for
you, just like the next branch did in the old repo? It should, but I
want to double-check before I ship 0.6.
That's it! Work continues on STS and I hope to have some kind of
functional code to publish soon.
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 5+ messages in thread* [sup-talk] sup news (including 0.6 release)
2008-07-31 2:10 [sup-talk] sup news (including 0.6 release) William Morgan
@ 2008-07-31 2:22 ` John Bent
2008-07-31 6:38 ` Richard Heycock
2008-07-31 7:14 ` Claes Nästén
2 siblings, 0 replies; 5+ messages in thread
From: John Bent @ 2008-07-31 2:22 UTC (permalink / raw)
Excerpts from William Morgan's message of Wed Jul 30 20:10:49 -0600 2008:
> If you don't have local changes, you can simply reclone it:
> git clone git://gitorious.org/sup/mainline.git
>
This worked for me except I got an error message and had to install
fastthread first. Thanks William and all for all your hard work on sup!
John
^ permalink raw reply [flat|nested] 5+ messages in thread
* [sup-talk] sup news (including 0.6 release)
2008-07-31 2:10 [sup-talk] sup news (including 0.6 release) William Morgan
2008-07-31 2:22 ` John Bent
@ 2008-07-31 6:38 ` Richard Heycock
2008-07-31 7:14 ` Claes Nästén
2 siblings, 0 replies; 5+ messages in thread
From: Richard Heycock @ 2008-07-31 6:38 UTC (permalink / raw)
Excerpts from William Morgan's message of Thu Jul 31 12:10:49 +1000 2008:
> Hi all,
>
> Some news:
>
> - I've moved Sup over to Gitorious. I don't know that this will
> magically spur a continuous stream of bugfixes, but at least now we
> have a repo webpage that's not broken.
>
> If you're running from Git, you should update your repo to pull from
> there.
>
> If you don't have local changes, you can simply reclone it:
> git clone git://gitorious.org/sup/mainline.git
>
> If you want to preserve your local repository, you can do something like:
> git remote add gitorious git://gitorious.org/sup/mainline.git
> git fetch
>
> Then for each branch that you want "git pull" to pull from gitorious,
> you'll need to do:
> git config branch.<branch>.remote gitorious
> git config branch.<branch>.merge refs/heads/<branch>
>
> and then check it out and try pulling. If you haven't made any
> commits, this should be a fast-forward.
>
> If you want to call the remote "origin" instead of "gitorious", you'll
> just have to remove or rename your origin remote first. The commands
> above will be the same.
>
> Note that I've reset the "next" branch, so if you have commits on that
> branch, life may be little more complicated. Doing the above and merging
> should work. Or you can isolate your changes somehow and rebase
> --onto, if you feel like being complicated.
>
> - I've merged all outstanding topic branches down to master, and
> cherry-picked a couple commits that somehow ended up in next by
> themselves. So master should be the latest and greatest for the
> moment.
>
> - I've moved the bugs dir directly into master. The bugs branch is now
> deprecated. (It doesn't even exist in the Gitorious repo.)
>
> - I'm planning on release an 0.6 soon with all the bugfixes we have so
> far. To this end, I've unassigned all unclosed issues from the 0.6
> release.
>
> - Can anyone confirm that that the master branch on gitorious works for
> you, just like the next branch did in the old repo? It should, but I
> want to double-check before I ship 0.6.
Works for me as well.
rgh
>
> That's it! Work continues on STS and I hope to have some kind of
> functional code to publish soon.
--
+61 (0) 410 646 369
[e]: rgh at neoss.com.au
[im]: rgh at jabber.org
You're worried criminals will continue to penetrate into cyberspace, and
I'm worried complexity, poor design and mismanagement will be there to meet
them - Marcus Ranum
^ permalink raw reply [flat|nested] 5+ messages in thread
* [sup-talk] sup news (including 0.6 release)
2008-07-31 2:10 [sup-talk] sup news (including 0.6 release) William Morgan
2008-07-31 2:22 ` John Bent
2008-07-31 6:38 ` Richard Heycock
@ 2008-07-31 7:14 ` Claes Nästén
2008-07-31 22:40 ` William Morgan
2 siblings, 1 reply; 5+ messages in thread
From: Claes Nästén @ 2008-07-31 7:14 UTC (permalink / raw)
Excerpts from William Morgan's message of Thu Jul 31 04:10:49 +0200 2008:
>
> - Can anyone confirm that that the master branch on gitorious works for
> you, just like the next branch did in the old repo? It should, but I
> want to double-check before I ship 0.6.
>
Works for me as well after re-creating the next branch (didn't have
anything to keep in it.)
--
Claes N?st?n, <me{@}pekdon.net>, http://www.pekdon.net/
"Money has corrupted so much in this world, life would be meaningless
if it kills music as well." - Bin?rpilot
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-07-31 22:40 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-07-31 2:10 [sup-talk] sup news (including 0.6 release) William Morgan
2008-07-31 2:22 ` John Bent
2008-07-31 6:38 ` Richard Heycock
2008-07-31 7:14 ` Claes Nästén
2008-07-31 22:40 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox