[1783] in athena10
Re: proposed report: 3/19/09
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Thu Mar 19 20:28:19 2009
Cc: debathena@mit.edu
Message-Id: <E15A6E4C-8D06-42F5-90CD-A1FF35A49F68@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Evan Broder <broder@mit.edu>
In-Reply-To: <49C2D908.6040107@mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 19 Mar 2009 20:27:19 -0400
> * debathena-login-graphical, debathena-login-workstation: We need to
> hammer out the language on the notice to debathena-announce. We should
> also incorporate a statement about Dapper into that e-mail before
> sending it. I'll put this about halfway down the list of things I
> intend
> to look at next week.
Is the statement about Dapper something about desupporting it? If so,
it may want two separate e-mails. I appreciate the need to keep
debathena-announce low traffic, but IME desupport announcements want
their own e-mail.
> * debathena-xdsc: I don't like this patch, because it feels like it's
> failing to understand the underlying problem. However, nobody seems to
> be interested in writing a better patch, so I'm inclined to go with
> memory leaks over crashing.
Out of curiosity, how many people use xdsc and actually prefer it over
diswww or emacs-discuss? It's kind of ancient, and I wonder if it
would be better re-written in Python or something?
-Jon
