From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: emacs-devel@gnu.org
Subject: Re: VMS support
Date: Thu, 24 Jul 2008 09:59:52 -0400 [thread overview]
Message-ID: <jwv1w1j5qww.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <873alz681f.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Thu, 24 Jul 2008 09:44:12 +0200")
> 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.
Good.
> 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.
The only meaningful merge in my mind is a merge with CVS trunk, not with
some previous released version of the code, otherwise you'll always have
to play catch up.
> 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).
I guess we should do the same for the Carbon port since it also seems
that nobody is interested in updating&maintaining it.
Stefan
next prev parent reply other threads:[~2008-07-24 13:59 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
2008-07-24 13:59 ` Stefan Monnier [this message]
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=jwv1w1j5qww.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ttn@gnuvola.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).