From: "Jérôme Marant" <jmarant@free.fr>
Cc: mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: The MH-E repository
Date: Tue, 31 May 2005 09:08:17 +0200 [thread overview]
Message-ID: <1117523297.429c0d614d0e3@imp4-q.free.fr> (raw)
In-Reply-To: <25625.1117492799@olgas.newt.com>
Selon Bill Wohler <wohler@newt.com>:
...
> Now that there is a separate lisp/mh-e directory, and all of the MH-E
> developers have signed papers and therefore should have write access or
> be able to get write access to the Emacs repository, I'd like to ask
> what folks think about moving the MH-E src module from SourceForge to
> gnu.org.
Hi,
I think this is a bad idea, especially for those who like to do regular
checkouts in order to have the cutting edge versions. There is no
really benefit.
I'll add that trying to integrate more and more lisp modules in Emacs
core is bad, and even worst since there are so few Emacs
releases that people always use more recent versions of modules
they grabbed from outside instead of the ones shipped with Emacs (for
example: Gnus, speedbar, ...).
To my mind, the good solution would be to ship modules in a separate
tarball and update them more frequently.
--
Jérôme Marant
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next prev parent reply other threads:[~2005-05-31 7:08 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 22:39 The MH-E repository Bill Wohler
2005-05-30 23:27 ` Juanma Barranquero
2005-05-31 0:21 ` Miles Bader
2005-05-31 7:08 ` Jérôme Marant [this message]
2005-05-31 7:46 ` Miles Bader
2005-05-31 8:17 ` Jérôme Marant
2005-05-31 8:59 ` Mark D. Baushke
2005-05-31 9:30 ` Jérôme Marant
2005-05-31 15:21 ` Bill Wohler
2005-05-31 9:03 ` Eli Zaretskii
2005-05-31 17:47 ` Richard Stallman
2005-05-31 20:00 ` Jérôme Marant
2005-06-01 17:22 ` Richard Stallman
2005-06-02 5:31 ` packaging (was: The MH-E repository) Janusz S. Bień
2005-06-03 8:01 ` Richard Stallman
2005-05-31 8:56 ` The MH-E repository Kim F. Storm
2005-05-31 10:07 ` Mark D. Baushke
2005-05-31 17:47 ` Richard Stallman
2005-05-31 18:16 ` Mark D. Baushke
2005-05-31 18:39 ` chad brown
2005-06-01 17:24 ` Richard Stallman
2005-05-31 22:00 ` Kim F. Storm
2005-05-31 13:08 ` Stefan Monnier
2005-05-31 17:09 ` Bill Wohler
2005-05-31 18:06 ` Mark D. Baushke
2005-05-31 19:13 ` Stefan Monnier
2005-07-05 4:35 ` Richard M. Stallman
2005-07-05 18:28 ` Bill Wohler
2005-07-11 1:22 ` Mark D. Baushke
2005-05-31 21:39 ` Miles Bader
2005-05-31 17:46 ` Richard Stallman
2005-06-01 9:39 ` Richard Stallman
2005-06-01 16:50 ` Bill Wohler
2005-06-02 6:40 ` Richard Stallman
2005-06-02 18:32 ` Bill Wohler
2005-06-03 22:30 ` Richard Stallman
2005-06-03 23:25 ` Bill Wohler
2005-06-04 9:44 ` [Savannah-help-public] " Sylvain Beucler
2005-06-04 12:30 ` Miles Bader
2005-06-04 16:13 ` Bill Wohler
2005-06-04 16:52 ` Sylvain Beucler
2005-09-30 22:49 ` Bill Wohler
2005-10-01 17:04 ` Sylvain Beucler
2005-10-03 23:14 ` Bill Wohler
2005-10-04 12:17 ` Sylvain Beucler
2005-10-04 20:13 ` Bill Wohler
2005-06-04 17:59 ` Richard Stallman
[not found] ` <wohler@newt.com>
2005-06-01 13:47 ` Peter S Galbraith
2005-06-01 14:27 ` Bill Wohler
2005-06-02 6:40 ` Richard Stallman
2005-09-16 19:12 ` Shall we use etc/images more? Peter S Galbraith
-- strict thread matches above, loose matches on Subject: below --
2005-09-07 2:37 Bill Wohler
2005-09-07 8:30 ` Kim F. Storm
[not found] ` <E1EDCMR-00043d-Vd@fencepost.gnu.org>
2005-09-08 5:47 ` Bill Wohler
2005-09-12 4:57 ` Richard M. Stallman
2005-09-12 6:07 ` Bill Wohler
2005-09-13 15:54 ` Richard M. Stallman
[not found] ` <E1EFD6x-0000cn-Qd@fencepost.gnu.org>
2005-09-14 1:50 ` Bill Wohler
2005-09-15 13:00 ` Richard M. Stallman
2005-09-15 18:36 ` Bill Wohler
2005-09-16 6:16 ` Richard M. Stallman
2005-09-30 18:00 ` Bill Wohler
2005-09-14 8:02 ` Chong Yidong
2005-09-14 8:55 ` Kim F. Storm
2005-09-14 23:54 ` Chong Yidong
2005-09-14 14:08 ` Kim F. Storm
2005-09-15 13:00 ` Richard M. Stallman
2005-09-16 2:28 ` Katsumi Yamaoka
2005-09-12 22:43 ` Bill Wohler
2005-09-13 9:23 ` Kim F. Storm
2005-09-13 19:51 ` Eli Zaretskii
2005-09-14 1:45 ` Bill Wohler
2005-09-14 6:41 ` Mark D. Baushke
2005-09-15 2:41 ` Richard M. Stallman
2005-09-15 18:48 ` Bill Wohler
2005-09-29 21:45 ` Bill Wohler
2005-09-30 0:40 ` Bill Wohler
2005-09-30 14:22 ` Chong Yidong
2005-09-30 20:01 ` Richard M. Stallman
2005-10-15 6:45 ` Bill Wohler
2005-10-15 15:00 ` Romain Francoise
2005-10-15 17:43 ` Bill Wohler
2005-10-15 18:52 ` Romain Francoise
2005-10-16 14:41 ` Richard M. Stallman
2005-10-16 18:00 ` Bill Wohler
2005-10-17 17:30 ` Richard M. Stallman
2005-10-17 22:21 ` lisp/toolbar is gone (was: Shall we use etc/images more?) Bill Wohler
2005-10-18 8:03 ` Andreas Schwab
2005-09-13 15:55 ` Shall we use etc/images more? 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=1117523297.429c0d614d0e3@imp4-q.free.fr \
--to=jmarant@free.fr \
--cc=emacs-devel@gnu.org \
--cc=jerome.marant@free.fr \
--cc=mh-e-devel@lists.sourceforge.net \
/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).