From: rgh@roughage.com.au (Richard Heycock)
Subject: [sup-talk] sup news (including 0.6 release)
Date: Thu, 31 Jul 2008 16:38:05 +1000 [thread overview]
Message-ID: <1217486240-sup-679@wrasse> (raw)
In-Reply-To: <1217466178-sup-1370@entry>
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
next prev parent reply other threads:[~2008-07-31 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 2:10 William Morgan
2008-07-31 2:22 ` John Bent
2008-07-31 6:38 ` Richard Heycock [this message]
2008-07-31 7:14 ` Claes Nästén
2008-07-31 22:40 ` William Morgan
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=1217486240-sup-679@wrasse \
--to=rgh@roughage.com.au \
/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