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: Thu, 24 Jul 2008 09:44:12 +0200	[thread overview]
Message-ID: <873alz681f.fsf@ambire.localdomain> (raw)
In-Reply-To: <jwv63qwgyjl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 23 Jul 2008 16:05:01 -0400")

() Stefan Monnier <monnier@iro.umontreal.ca>
() Wed, 23 Jul 2008 16:05:01 -0400

   The only question that I think is really relevant is: is there
   some hope that someone will pursue this work (both the
   copyright assignment issue and the update of the code to the
   Emacs-CVS-trunk codebase) in some foreseeable future.

Personally speaking, there is hope, in two parts:

a/ I received a clarification about the nuances between
   "disclaiming interest" and "copyright assignment" from the FSF
   copyright clerk (thanks!), which can be summed up (IIUC) as:
   Richard Levitte's code is ok to use, if i copyright the
   (extensive) changes i've made to it, since i myself have done
   the past/future assignment.

b/ I have a soft spot for VMS, though that spot shrinks w/ time.
   If i can finangle a $ituation to provide a port of Emacs 22 (or
   Emacs 23, once it settles), i will do it, otherwise no.

Having said that, i haven't queried potential funders yet, and the
negotiation process may take a while, and it may ultimately block
indefinitely, so "in some foreseeable future" is not indicated.

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

If anyone reading this is in a position to expedite b/ (above),
please feel free to contact me privately.

thi




  reply	other threads:[~2008-07-24  7:44 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
2008-07-23 20:05       ` Stefan Monnier
2008-07-24  7:44         ` Thien-Thi Nguyen [this message]
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=873alz681f.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).