From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Sup 0.12.1 released
Date: Mon, 24 Jan 2011 12:39:50 -0500 [thread overview]
Message-ID: <1295890080-sup-6272@masanjin.net> (raw)
In-Reply-To: <1295876398-sup-4348@midna.zekjur.net>
Reformatted excerpts from Michael Stapelberg's message of 2011-01-24:
> Does that mean we should CC William when sending patches now?
You can CC me if you like, but it won't help. :)
I have a little more time for Sup nowadays than before. But I would
rather spend it working on features (including possible a new index
backend.)
So if there's anyone who would be interested in the maintainership
busywork of collecting patches, making branches, and pushing releases,
please let me know.
--
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-24 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 6:05 Rich Lane
2011-01-24 6:25 ` Rich Lane
2011-01-24 13:40 ` Michael Stapelberg
2011-01-24 17:39 ` William Morgan [this message]
2011-01-24 17:27 ` William Morgan
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=1295890080-sup-6272@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