unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: emacs-devel@gnu.org
Subject: Re: VMS support
Date: Wed, 23 Jul 2008 12:27:33 +0200	[thread overview]
Message-ID: <87k5fcc2ui.fsf@ambire.localdomain> (raw)
In-Reply-To: <8763qznhfd.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 21 Jul 2008 15:52:38 -0400")

() Chong Yidong <cyd@stupidchicken.com>
() Mon, 21 Jul 2008 15:52:38 -0400

   What is the situation with the VMS support?  AFAICT, ttn was working
   on getting it to work again, but I haven't heard anything about this
   project since.

Emacs 21.2 was the last known-good port, but that requires out-of-tree
code due to legal issues (specifically: the author of a big chunk of
VMS-specific code filed in 1992 a "copyright disclaimer" only, which is
not equal in force to a "copyright assignment" IIUC, and repeated
attempts to get the (standard) past/future copyright assignment from him
(by me and perhaps others) have failed, even though he has indicated in
200[45]-ish email that he is willing to do so).  These legal issues
might still be resolvable (i can try engaging him again), but i cannot
say for sure.

More details, including (lack-of-)progress/technical info, are at:
http://www.gnuvola.org/software/emacs-for-vms/

   Dan Nicolaescu has suggested removing VMS support for the purpose of
   code cleanup.  WDYT?

I think removing VMS support is fine, but not for the purpose of code
cleanup.  That reason implies that clean VMS support should be kept.
A better reason is that VMS is proprietary and Emacs users on VMS have
not shown sufficient interest in it.

If VMS support is to be removed, please do a complete job and remove it
from the Lisp and config/build/doc/admin parts of Emacs, as well.

thi




  reply	other threads:[~2008-07-23 10:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87iquzmcxm.fsf@stupidchicken.com>
     [not found] ` <87d4l76ntu.fsf@ambire.localdomain>
2008-07-21 19:52   ` VMS support Chong Yidong
2008-07-23 10:27     ` Thien-Thi Nguyen [this message]
2008-07-23 20:05       ` Stefan Monnier
2008-07-24  7:44         ` Thien-Thi Nguyen
2008-07-24 13:59           ` Stefan Monnier
2008-07-24 16:55             ` Dan Nicolaescu
2008-07-24 19:58               ` Stefan Monnier
2008-07-27 18:41                 ` Dan Nicolaescu
2008-07-27 18:48                   ` Stefan Monnier
2008-07-27 19:06                     ` Dan Nicolaescu
2008-07-27 19:31                       ` Stefan Monnier
2008-07-27 19:51                         ` Dan Nicolaescu
2008-07-27 20:44                           ` Stefan Monnier
2008-07-27 21:41                             ` Dan Nicolaescu
2008-07-28  9:15                           ` Thien-Thi Nguyen
2008-07-24 17:34             ` Thien-Thi Nguyen
2008-07-24 20:00               ` Stefan Monnier
2008-07-24 20:40                 ` Thien-Thi Nguyen
2008-07-24  2:23       ` Richard M Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k5fcc2ui.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).