unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: nickrob@snap.net.nz, karl@freefriends.org,
	andreas.roehler@online.de, emacs-devel@gnu.org
Subject: Re: elib -> emacs
Date: Wed, 20 Jun 2007 09:28:24 -0400	[thread overview]
Message-ID: <E1I10ES-0002cJ-Rc@fencepost.gnu.org> (raw)
In-Reply-To: <86ejk8ru3q.fsf@lola.quinscape.zz> (message from David Kastrup on Tue, 19 Jun 2007 14:45:13 +0200)

    I cannot see (judging from current postings rather than actually
    looking at the code) that adding elib as a separate entity is going to
    help consolidating this situation.  It very much sounds like the way
    to go about this would be to check whether we can get papers for it,
    and if we can, break it down for reusable pieces that we pull into
    subr.el and the Elisp manual.

We do have papers for Elib, and that's pretty much the way I think we
should handle it.  (I don't think it all has to go into subr.el.)

  reply	other threads:[~2007-06-20 13:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16  0:29 elib -> emacs Karl Berry
2007-06-16 19:19 ` Andreas Röhler
2007-06-17 21:49   ` Richard Stallman
2007-06-18  5:54     ` Andreas Röhler
2007-06-18  6:05       ` Nick Roberts
2007-06-18  8:08         ` Andreas Röhler
2007-06-19 10:41           ` Richard Stallman
2007-06-19 12:28             ` Andreas Röhler
2007-06-19 12:45               ` David Kastrup
2007-06-20 13:28                 ` Richard Stallman [this message]
2007-06-19 14:12               ` Stefan Monnier
2007-06-18 21:30       ` Richard Stallman
2007-06-24  1:40     ` T. V. Raman
2007-06-24 17:35       ` Richard Stallman
2007-06-24 22:36         ` T. V. Raman
2007-06-25 13:19           ` Richard Stallman
2007-08-26 14:13             ` Thien-Thi Nguyen
2007-08-26 14:25               ` Thien-Thi Nguyen
2007-08-27  4:19               ` Stefan Monnier
2007-06-24 22:39         ` T. V. Raman
2007-06-24 22:44         ` T. V. Raman
2007-06-25  8:31           ` Thien-Thi Nguyen
2007-06-18 15:36   ` Stefan Monnier
2007-06-18 18:59     ` Andreas Röhler
2007-06-19 22:25     ` Richard Stallman
2007-06-20  1:12       ` Stefan Monnier
2007-06-20 17:35         ` Richard Stallman
2007-06-20 18:07           ` Andreas Röhler
2007-06-20 19:17             ` Andreas Röhler
2007-06-21 17:32             ` Richard Stallman
2007-06-22  3:35         ` Michael Olson
2007-06-19 22:26     ` Richard 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=E1I10ES-0002cJ-Rc@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=andreas.roehler@online.de \
    --cc=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.org \
    --cc=nickrob@snap.net.nz \
    /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).