From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] call for new maintainers
Date: Wed, 26 Jan 2011 10:18:59 -0500 [thread overview]
Message-ID: <1296054871-sup-9586@masanjin.net> (raw)
In-Reply-To: <1295896722-sup-5870@midna.zekjur.net>
Reformatted excerpts from Michael Stapelberg's message of 2011-01-24:
> I don’t have enough time to be the only person doing this, but I do
> offer my help on reviewing/merging patches. Maybe having more than one
> guy with commit access turns out to be a good thing?
Yeah, maybe that's the right idea.
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. Then you can bypass the list mailing list for patches
entirely, which will save me a lot of work.
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.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-01-26 15:19 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 [this message]
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
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=1296054871-sup-9586@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--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