From: Sascha Silbe <sascha-ml-reply-to-2011-2@silbe.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] call for new maintainers
Date: Fri, 04 Mar 2011 13:16:41 +0100 [thread overview]
Message-ID: <1299240549-sup-530@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <1296054871-sup-9586@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]
Excerpts from William Morgan's message of Wed Jan 26 16:18:59 +0100 2011:
> So let's try this. Michael, Tero, Sascha, Edward, and everyone else
> who's had code make it into Sup successfully... if you send me your
> Gitorious usernames, I will add you to the Sup group and you will have
> push access.
I've finally created a gitorious account. I don't quite like the wording
of the ToS [1] concerning licenses (the way I read it Gitorious AS is
allowed to redistribute my code using a proprietary license), but
then the sup repository with all my submitted patches already is hosted
by them...
> Then you can bypass the list mailing list for patches
> entirely, which will save me a lot of work.
I'm happy to push my patches, but I'd still prefer to get at least one
Reviewed-By to make sure my changes are kosher.
> All I ask is that you divide things into nice topic branches and merge
> them into next but not master. I'll merge individual branches into
> master when prepping for a release.
Noted.
Sascha
[1] http://en.gitorious.org/tos/
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-03-04 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 18:40 William Morgan
2011-01-24 19:20 ` Michael Stapelberg
2011-01-26 15:18 ` William Morgan
2011-01-26 16:10 ` Ben Walton
2011-01-26 18:13 ` William Morgan
2011-01-26 23:44 ` Hamish D
2011-01-27 7:31 ` Tero Tilus
2011-01-28 6:20 ` William Morgan
2011-03-04 9:05 ` Damien Leone
2011-03-07 18:27 ` William Morgan
2011-03-04 12:16 ` Sascha Silbe [this message]
2011-03-04 12:19 ` Sascha Silbe
2011-03-07 18:27 ` William Morgan
2011-01-25 14:19 ` [sup-talk] " Wael M. Nasreddine
2011-01-25 17:04 ` [sup-devel] Fwd: " Wael Nasreddine
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=1299240549-sup-530@xo15-sascha.sascha.silbe.org \
--to=sascha-ml-reply-to-2011-2@silbe.org \
--cc=sup-devel@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