[14525] in SIPB bug reports
Re: Housekeeping
daemon@ATHENA.MIT.EDU (chad brown)
Tue Jul 20 17:27:31 2004
From y@MIT.EDU Tue Jul 20 21:27:30 2004
Return-Path: <y@MIT.EDU>
Delivered-To: bug-sipb-mtg@CHARON.mit.edu
Received: (qmail 22826 invoked from network); 20 Jul 2004 21:27:30 -0000
Received: from fort-point-station.mit.edu (18.7.7.76)
by charon.mit.edu with SMTP; 20 Jul 2004 21:27:30 -0000
Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])
by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id i6KLRTmZ019013;
Tue, 20 Jul 2004 17:27:29 -0400 (EDT)
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
by grand-central-station.mit.edu (8.12.4/8.9.2) with ESMTP id i6KLRRPD024682;
Tue, 20 Jul 2004 17:27:27 -0400 (EDT)
Received: from [192.168.1.103] (h000625f9896f.ne.client2.attbi.com [24.61.138.250])
)
by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i6KLRQRg008475;
Tue, 20 Jul 2004 17:27:26 -0400 (EDT)
In-Reply-To: <200407202059.i6KKxwOr027358@zygorthian-space-raiders.mit.edu>
References: <200407202059.i6KKxwOr027358@zygorthian-space-raiders.mit.edu>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <96B5FB52-DA93-11D8-A60A-000393DEF2CA@mit.edu>
Content-Transfer-Encoding: 7bit
Cc: bug-sipb@MIT.EDU
From: chad brown <y@MIT.EDU>
Subject: Re: Housekeeping
Date: Tue, 20 Jul 2004 17:27:23 -0400
To: Mike Rolish <merolish@MIT.EDU>
X-Mailer: Apple Mail (2.618)
sipb pine is functionally different from athena pine. There seem to be
people who prefer the sipb pine functionality (I know a few of these).
I would recommend trying to find out why, and then perhaps `fix' the
`issue' with athena pine. Just a recommendation.
*chad
On 20 Jul, 2004, at 16:59, Mike Rolish wrote:
> The recent ncurses/less issue got me wondering how many of the programs
> in the sipb locker are also in the release. They are listed below. I
> recommend that they all be removed unless there is good reason not to
> do
> so. With a few exceptions, they're only symlinks to earlier arches and
> older versions than their counterparts in the release.
>
> I particularly support retiring SIPB pine.
>
> -Mike