From: Gaute Hope <eg@gaute.vetsj.com>
To: James Pearson <pearson@changedmy.name>
Cc: sup-talk <sup-talk@rubyforge.org>,
Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] Release 0.13.1
Date: Sat, 22 Jun 2013 12:48:13 +0200 [thread overview]
Message-ID: <1371897680-sup-4189@qwerzila> (raw)
In-Reply-To: <CA+ds9gJCfauTgS1LvrsOF0QREAKh9pKy=a550nj=1ZNi7wBvzA@mail.gmail.com>
Excerpts from James Pearson's message of 2013-06-22 04:10:29 +0200:
> I was going to ask why the tags on the Gitorious repo[0] hadn't been
> updated, when I visited the (new!) website and saw that development has
> moved onto Github[1] (and restarted!). I'm apparently very behind the
> times - and perhaps now I should dig out those changes I made and submit
> them...
>
> Glad to see things moving along again.
> - P
>
> [0]: http://gitorious.org/sup/mainline
> [1]: https://github.com/sup-heliotrope/sup
Yup! Dig 'em up. We generally prefer pull requests [0] now a days. Also,
we've collected contribution/development resources in the new wiki [1].
I have asked William if he would agree to redirect to/mention the new setup
in the old gitorious repo. He gave me access to the sup-team, but I am
unfortunately not allowed to make any admin changes to the repository.
Regards, Gaute
[0] https://github.com/sup-heliotrope/sup/pulls
[1] https://github.com/sup-heliotrope/sup/wiki/Development
next prev parent reply other threads:[~2013-06-22 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 12:07 Gaute Hope
2013-06-22 2:10 ` [sup-talk] " James Pearson
2013-06-22 10:48 ` Gaute Hope [this message]
2013-06-30 21:22 ` [sup-devel] " Hamish D
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=1371897680-sup-4189@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=pearson@changedmy.name \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
/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