From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: VMS support Date: Thu, 24 Jul 2008 09:55:44 -0700 Message-ID: <200807241655.m6OGtiqp008494@sallyv1.ics.uci.edu> References: <87iquzmcxm.fsf@stupidchicken.com> <87d4l76ntu.fsf@ambire.localdomain> <8763qznhfd.fsf@stupidchicken.com> <87k5fcc2ui.fsf@ambire.localdomain> <873alz681f.fsf@ambire.localdomain> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1216918651 27150 80.91.229.12 (24 Jul 2008 16:57:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 24 Jul 2008 16:57:31 +0000 (UTC) Cc: Thien-Thi Nguyen , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 24 18:58:20 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KM48j-0007zK-QF for ged-emacs-devel@m.gmane.org; Thu, 24 Jul 2008 18:58:06 +0200 Original-Received: from localhost ([127.0.0.1]:49260 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KM47p-0003nS-5m for ged-emacs-devel@m.gmane.org; Thu, 24 Jul 2008 12:57:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KM47k-0003lh-U4 for emacs-devel@gnu.org; Thu, 24 Jul 2008 12:57:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KM47k-0003kW-5F for emacs-devel@gnu.org; Thu, 24 Jul 2008 12:57:04 -0400 Original-Received: from [199.232.76.173] (port=41927 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KM47k-0003kM-00 for emacs-devel@gnu.org; Thu, 24 Jul 2008 12:57:04 -0400 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]:57529) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1KM47j-0007oO-Hq for emacs-devel@gnu.org; Thu, 24 Jul 2008 12:57:03 -0400 X-ICS-MailScanner-Watermark: 1217523345.65486@LaY/PEmFhF/WGUWsE0jbTw Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m6OGtiqp008494; Thu, 24 Jul 2008 09:55:44 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Thu, 24 Jul 2008 09:59:52 -0400") Original-Lines: 24 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:101406 Archived-At: Stefan Monnier writes: > > I say go ahead and zonk the VMS support. If someone funds another > > port (by me or whoever), previous source can always be re-dredged > > and previous "expertise" can always be re-fudged. :-D > > OK, so we should get rid of the VMS code in one clean commit with a CVS > tag before and another after. I think it's important for this commit to > be as clean as possible (i.e. it really removes all the VMS related > code and text), so that there won't be some future changes that remove > a bit more of the VMS support: this way the CVS tags will faithfully > include all the relevant code (and text). IMO doing it this way is too high of a burden and hence not very feasible. It pretty much forces this to be a one person job instead of allowing it to be distributed. There are 397 references just to the VMS string just in the C code + docs. And there are probably many things that are only valid for VMS, but are not explicitly mentioning the VMS string. > I guess we should do the same for the Carbon port since it also seems > that nobody is interested in updating&maintaining it. Is this a go ahead?