Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Doing some...  maintenance
Date: Mon, 30 Aug 2010 18:25:01 +0200	[thread overview]
Message-ID: <m3wrr8rrtu.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87eidgqljs.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> LMI> Should I just go ahead and do a deleting spree?
>
> Yes.  Have no fear, see
> http://stackoverflow.com/questions/953481/restore-a-deleted-file-in-a-git-repo

So we can start with backends.  I think the way to do this is to remove
them one at a time -- that is, delete the backend file, and then delete
all mentions of it from the rest of the source code and the
documentation.

Here's the complete list of backends:

nnagent.el
nnbabyl.el
nndb.el
nndiary.el
nndir.el
nndoc.el
nndraft.el
nneething.el
nnfolder.el
nngateway.el
nnimap.el
nnir.el
nnkiboze.el
nnlistserv.el
nnmaildir.el
nnmairix.el
nnmbox.el
nnmh.el
nnml.el
nnnil.el
nnrss.el
nnslashdot.el
nnsoup.el
nnspool.el
nntp.el
nnultimate.el
nnvirtual.el
nnwarchive.el
nnweb.el
nnwfm.el

Yikes.  Anyway, I think the candidates for deletion are:

nndb.el        mostly not updated since 1997.  Goner, I think
nnkiboze.el    I can't really imagine anybody uses this
nnlistserv.el  This, neither
nnslashdot.el  Does this even work?  nnrss/Gwene is an alternative
nnsoup.el      Way old code
nnultimate.el  I can't imagine this works still
nnwarchive.el  Very little updating since 1999
nnwfm.el       Ditto

So I'm going to delete these eight backends (and some of them have
gnus-*.el files corresponding to them, like gnus-soup.el), unless
anybody objects.  Speak up now etc.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2010-08-30 16:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29 16:47 Lars Magne Ingebrigtsen
2010-08-29 16:50 ` Greg Troxel
2010-08-29 17:03   ` Lars Magne Ingebrigtsen
2010-08-29 17:39 ` David Engster
2010-08-30 13:25 ` Ted Zlatanov
2010-08-30 16:25   ` Lars Magne Ingebrigtsen [this message]
2010-08-30 17:13     ` Leo
2010-08-30 17:16       ` Lars Magne Ingebrigtsen
2010-08-30 17:27         ` Leo
2010-08-30 17:34           ` Lars Magne Ingebrigtsen
2010-08-30 17:37             ` Leo
2010-08-31  6:25       ` Reiner Steib
2010-08-31  9:40     ` Alberto Luaces
2010-08-31 12:53       ` Lars Magne Ingebrigtsen
2010-08-31 15:59     ` Lars Magne Ingebrigtsen
2010-09-01 16:32     ` Lars Magne Ingebrigtsen
2010-09-01 17:03       ` Lars Magne Ingebrigtsen
2010-09-01 17:13         ` Ted Zlatanov
2010-09-01 17:16           ` Lars Magne Ingebrigtsen

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=m3wrr8rrtu.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).