From: "Eli Zaretskii" <eliz@gnu.org>
Cc: savannah-hackers@gnu.org, emacs-devel@gnu.org
Subject: Re: [Savannah-hackers] Re: Improvement in emacs-diffs list
Date: Sun, 12 Dec 2004 23:33:03 +0200 [thread overview]
Message-ID: <01c4e092$Blat.v2.2.2$4e5bc2a0@zahav.net.il> (raw)
In-Reply-To: <20041212074913.GC6615@dink.localdomain> (message from Sylvain Beucler on Sun, 12 Dec 2004 08:49:13 +0100)
> Date: Sun, 12 Dec 2004 08:49:13 +0100
> From: Sylvain Beucler <beuc@gnu.org>
> Cc: rms@gnu.org, savannah-hackers@gnu.org, emacs-devel@gnu.org
>
> > > Thanks to the Savannah hackers team, emacs-diffs should now receive
> > > notifications only for changes to the trunk.
> >
> > Does that mean that I need to remove myself from emacs-trunk-diffs and
> > resubscribe to emacs-diffs?
>
> Actually I wasn't aware that this mailing-list, created for testing
> purposes, was used by other developers.
I didn't know about emacs-trunk-diffs until I saw its name cited in a
thread on emacs-devel. Then I recalled my old gripe about large
chunks of irrelevant diffs being sent to emacs-diffs, and said to
myself: great, they finally created a solution for that, but just
forgot to advertize it, or maybe some mail disaster prevented me from
seing the announcement. And since lists.gnu.org happily let me
subscribe, I never looked back...
> RMS asked me to delete emacs-trunk-diffs, so you need to subscribe to
> emacs-diffs again.
Done, thanks.
next prev parent reply other threads:[~2004-12-12 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 18:26 Improvement in emacs-diffs list Richard Stallman
2004-12-12 4:59 ` Eli Zaretskii
2004-12-12 7:49 ` [Savannah-hackers] " Sylvain Beucler
2004-12-12 21:33 ` Eli Zaretskii [this message]
[not found] ` <m3pt1go0pt.fsf@kfs-l.imdomain.dk>
2004-12-12 7:45 ` Sylvain Beucler
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='01c4e092$Blat.v2.2.2$4e5bc2a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=savannah-hackers@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).