public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Alan Dorman <mdorman@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Microsoft and Xenix.
Date: 23 Jun 2001 20:13:13 -0400	[thread overview]
Message-ID: <877ky2ohuu.fsf@amanda.mallet-assembly.org> (raw)
In-Reply-To: <E15DZbq-0008D8-00@roo.home> <01062310075401.00696@localhost.localdomain>
In-Reply-To: <01062310075401.00696@localhost.localdomain>

Rob Landley <landley@webofficenow.com> writes:
> That would be the X version of emacs.  And there's the explanation
> for the split between GNU and X emacs: it got forked and the
> closed-source version had a vew years of divergent development
> before opening back up, by which point it was very different to
> reconcile the two code bases.

No, sorry, wrong, for at least a couple of reasons reasons:

 1) XEmacs, being constrained to be under the same license (GPL) as
    its progenitor, GNU Emacs, could never have been closed-source.

 2) Lucid Emacs, the version of Emacs that becamse XEmacs, was not
    started until ca. 1992

    I refer you to http://www.jwz.org/doc/emacs-timeline.html for
    documentation---JWZ was Mr. Lucid Emacs for quite a time.

In 1987, there are any number of things that it could have been---I'd
guess either Unipress Emacs or perhaps Gosling Emacs.

Mike.

  reply	other threads:[~2001-06-24  0:14 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 22:41 Microsoft and Xenix Alan Chandler
2001-06-23 14:07 ` Rob Landley
2001-06-24  0:13   ` Michael Alan Dorman [this message]
2001-06-24 14:18     ` Rob Landley
2001-06-25  1:45       ` Jeff Dike
2001-06-24 20:51         ` Rob Landley
2001-06-24  0:49   ` John Adams
2001-06-24 14:25     ` Rob Landley
2001-06-24  2:47   ` Eric W. Biederman
2001-06-24 10:36     ` Rob Landley
2001-06-24 22:20       ` [OT] " Daniel Phillips
2001-06-25  3:38         ` Michal Jaegermann
2001-06-24 22:41       ` Chris Meadors
2001-06-24 21:13         ` Microsoft and Xenix - Now there's a mailing list for this discussion Rob Landley
2001-06-25  0:55       ` Microsoft and Xenix William T Wilson
2001-06-25 17:11         ` asmith
2001-06-25 18:18           ` Robert J.Dunlop
2001-06-25  3:17       ` Eric W. Biederman
2001-07-02 10:04       ` Juan Quintela
2001-06-25 19:23   ` Kai Henningsen
2001-06-26 15:16     ` Rob Landley
2001-06-26 21:26       ` Michael Meissner
2001-06-27  8:09         ` Geert Uytterhoeven
2001-06-27 18:07           ` Peter De Schrijver
2001-06-27 13:43         ` Peter Bergner
2001-06-28 21:11     ` Thomas Dodd
2001-06-23 17:57 ` Mike Jagdis
2001-06-23 17:11   ` Rob Landley
  -- strict thread matches above, loose matches on Subject: below --
2001-06-24  2:41 Wayne.Brown
2001-06-24  3:07 ` Mike Castle
2001-06-24 14:44   ` Rob Landley
2001-06-25 15:13     ` Joel Jaeggli
2001-06-25 14:17       ` Rob Landley
2001-06-25 19:57         ` Erik Mouw
2001-06-27  2:10         ` Steve Underwood
2001-06-25 19:30     ` Kai Henningsen
2001-06-25 20:19       ` asmith
2001-06-24 14:32 ` Rob Landley
2001-06-24  2:59 Wayne.Brown
2001-06-25  2:51 Wayne.Brown
2001-06-24 23:21 ` Rob Landley
2001-06-25 17:14 ` asmith
2001-06-25 14:54   ` Rob Landley
2001-06-25 17:29 Wayne.Brown
2001-06-26  3:21 Jocelyn Mayer
2001-06-26 15:15 ` Joel Jaeggli
2001-06-26 16:15   ` Daniel Phillips
2001-06-26 16:42     ` Rob Landley

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

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

  git send-email \
    --in-reply-to=877ky2ohuu.fsf@amanda.mallet-assembly.org \
    --to=mdorman@debian.org \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox