From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] RFC: Nuke remote sources
Date: Mon, 18 Jan 2010 12:06:28 -0500 [thread overview]
Message-ID: <1263834319-sup-3032@masanjin.net> (raw)
In-Reply-To: <1263760710-sup-5382@masanjin.net>
Reformatted excerpts from William Morgan's message of 2010-01-17:
> Yeah, another thing to add to 0.10... sigh.
On second thought, I'm going to wait to 0.12 to remove this, and add the
deprecation notice on 0.11. The poor guy with a ferret index and
multiple IMAP sources should have a fighting chance.
I'm also going to try and spend less time between releases...
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-01-18 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 18:50 Rich Lane
2010-01-17 18:50 ` [sup-devel] [PATCH 1/3] remove mbox+ssh source Rich Lane
2010-01-17 18:50 ` [sup-devel] [PATCH 2/3] remove imap source Rich Lane
2010-01-17 18:50 ` [sup-devel] [PATCH 3/3] simplify sup-add Rich Lane
2010-01-17 20:39 ` [sup-devel] RFC: Nuke remote sources William Morgan
2010-01-18 17:06 ` William Morgan [this message]
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=1263834319-sup-3032@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