From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] call for new maintainers
Date: Wed, 26 Jan 2011 11:10:53 -0500 [thread overview]
Message-ID: <1296058113-sup-7048@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1296054871-sup-9586@masanjin.net>
Excerpts from William Morgan's message of Wed Jan 26 10:18:59 -0500 2011:
Hi William,
> 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.
I think it would be nicer to still see all patches posted to the list
first, regardless of committer rights. It's nice to see what people
are doing and be able to comment on proposed changes.
This doesn't preclude pushing to a topic branch as well, but it's
easier to comment on something if you don't need to track all of those
branches too...
Just a thought.
I'm bwalton on gitorious, btw.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-01-26 16: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
2011-01-26 16:10 ` Ben Walton [this message]
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=1296058113-sup-7048@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--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