From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, ding@gnus.org, alexander.pohoyda@gmx.net,
miles@gnu.org
Subject: Re: [rmail-mbox-branch]: mail-utils
Date: Mon, 11 Oct 2004 12:45:43 -0400 [thread overview]
Message-ID: <E1CH3It-0000t7-UG@fencepost.gnu.org> (raw)
In-Reply-To: <20041010225828.GA31829@fencepost> (message from Miles Bader on Sun, 10 Oct 2004 18:58:28 -0400)
I'm not sure what the difference between "contribute new changes" and
"install new versions" is.
In the gnus directory, the Gnus developers occasionally copy in new
versions of the files. (They look first for changes on our side that
ought not to be lost.) But they should not do this for files
outside the gnus directory.
Do you mean that a patch from a gnus maintainer would have to be
posted to the mailing list to be put into emacs (unlike Gnus
changes)?
I mean they should treat these files the same way they treat all the
other Lisp files that are not part of Gnus. That does not mean ALL
changes have to be discussed. They can install local uncontroversial
bug fixes without discussion, just as any of us would. However,
beyond that, they ought to post on this list.
next prev parent reply other threads:[~2004-10-11 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1096006177.432792.29828.nullmailer@Update.UU.SE>
[not found] ` <m3mzzgw2za.fsf@kfs-l.imdomain.dk>
[not found] ` <1096014084.739640.30529.nullmailer@Update.UU.SE>
[not found] ` <m3fz58vx3l.fsf@kfs-l.imdomain.dk>
[not found] ` <E1CB6fb-0004I5-Ud@fencepost.gnu.org>
[not found] ` <200410031040.i93Ae1YS000609@oak.pohoyda.family>
[not found] ` <E1CEUc7-0003aQ-C3@fencepost.gnu.org>
[not found] ` <87d5zvwmq9.fsf_-_@oak.pohoyda.family>
[not found] ` <20041006214742.GA5180@fencepost>
[not found] ` <87mzywyeau.fsf@oak.pohoyda.family>
2004-10-08 23:47 ` Miles Bader
2004-10-09 16:04 ` Alexander Pohoyda
2004-10-09 17:12 ` Stefan
2004-10-09 18:15 ` Alexander Pohoyda
2004-10-09 18:20 ` Miles Bader
[not found] ` <878yaf61x0.fsf@oak.pohoyda.family>
2004-10-09 21:10 ` Miles Bader
2004-10-09 21:19 ` Miles Bader
2004-10-10 15:15 ` Richard Stallman
2004-10-10 22:58 ` Miles Bader
2004-10-11 16:45 ` Richard Stallman [this message]
2004-10-12 2:09 ` Miles Bader
[not found] ` <87is9gj8v5.fsf@jurta.org>
[not found] ` <20041012150351.GA24206@fencepost>
2004-10-12 16:05 ` Syncing Gnus with Emacs and back (was: [rmail-mbox-branch]: mail-utils) Reiner Steib
2004-10-13 1:26 ` Syncing Gnus with Emacs and back Miles Bader
2004-10-13 20:21 ` Reiner Steib
2004-10-13 22:51 ` Miles Bader
2004-10-14 7:47 ` Miles Bader
2004-10-09 19:02 ` [rmail-mbox-branch]: mail-utils Stefan
2004-10-11 10:36 ` Simon Josefsson
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=E1CH3It-0000t7-UG@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=alexander.pohoyda@gmx.net \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@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.
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 NNTP newsgroup(s).