From: Christian Dietrich <stettberger@dokucode.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup for sale
Date: Thu, 25 Feb 2010 16:32:39 +0100 [thread overview]
Message-ID: <1267111506-sup-1389@peer.zerties.org> (raw)
In-Reply-To: <1267109223-sup-351@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 1223 bytes --]
Excerpts from William Morgan's message of Thu Feb 25 15:51:55 +0100 2010:
> But if someone wants to take the ball and be an official maintainer, I
> will give you my blessing and the power to gem push new releases. You
> don't even have to maintain my current crazy branching scheme!
Hi,
i haven't contributed much to sup yet (except one patch, that wasn't
applied) but i thinks its a really great mailer, that is it worth to
be activly continued.
In the last half year i made the experience that it is easier for
the single programmer (pusher) if he isn't the only one who is
allowed to push the upstream repository. Because there you have
always the possibility to say: Hm, i don't have the time in the next
3 weeks or so, but there is somebody else, who does merging/patching
and bugfixing. Perhaps it isn't that bad to give push right to a
group of people, who activly developed sup in the past.
Just my 2 cents
greetz didi
> Otherwise, things will continue as they do now.
I would really like to do more developing in sup, but without
getting your patches applied its a little bit frustrating.
--
No documentation is better than bad documentation
-- Das Ausdrucken dieser Mail wird urheberrechtlich verfolgt.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 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:[~2010-02-25 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 14:51 William Morgan
2010-02-25 15:32 ` Christian Dietrich [this message]
2010-09-23 11:50 ` Gaute Hope
2010-09-23 17:46 ` Alvaro Herrera
2010-10-06 22:47 ` Michael Stapelberg
2010-10-07 3:08 ` Rich Lane
2010-02-25 20:04 ` Tero Tilus
2010-02-25 21:55 ` Rich Lane
2010-02-25 23:26 ` William Morgan
2010-02-26 14:05 ` William Morgan
2010-02-26 16:07 ` Tero Tilus
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=1267111506-sup-1389@peer.zerties.org \
--to=stettberger@dokucode.de \
--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