unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: David Reitter <david.reitter@gmail.com>
Cc: Lennart Borgman <lennart.borgman@gmail.com>,
	rms@gnu.org, emacs-devel@gnu.org
Subject: Re: The current rules for making Emacs binaries available on the net?
Date: Sun, 16 May 2010 15:38:51 +0900	[thread overview]
Message-ID: <87mxw0gxl0.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <9B30A326-3575-409D-B989-7D981A845C8D@gmail.com>

David Reitter writes:

 > In my experience, binary distributions are not necessarily
 > productive in that sense.

But remember that an Emacs "binary" distribution usually contains
source Lisp[1], and coding Lisp is the most productive way for
newcomers to contribute (and some oldtimers, too, hello Drew! :-)
Even if they've never done it before; the Emacs C code is full of
strange constructs like DEFUN and redisplay and Mule and GCPRO, and
even experienced C hackers can get turned around in it.

Footnotes:

[1] I was disgusted to discover that Ubuntu packages for my Sharp
Netwalker don't contain source for XEmacs core Lisp.




      reply	other threads:[~2010-05-16  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 13:40 The current rules for making Emacs binaries available on the net? Lennart Borgman
2010-05-14 21:03 ` Richard Stallman
2010-05-14 22:51   ` Lennart Borgman
2010-05-15 20:27     ` Richard Stallman
2010-05-15 21:51     ` David Reitter
2010-05-16  6:38       ` Stephen J. Turnbull [this message]

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=87mxw0gxl0.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=rms@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).