unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-diffs Digest, Vol 11, Issue 100
Date: 16 Oct 2003 17:23:16 +0900	[thread overview]
Message-ID: <buobrsha8wb.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <3405-Thu16Oct2003082755+0200-eliz@elta.co.il>

"Eli Zaretskii" <eliz@elta.co.il> writes:
> >    1. Changes to emacs/man/custom.texi [lexbind] (Miles Bader)
> >    2. Changes to emacs/lisp/net/tramp-util.el [lexbind] (Miles Bader)
> >    3. Changes to emacs/lisp/menu-bar.el [lexbind] (Miles Bader)
> >    4. Changes to emacs/src/s/cxux7.h [lexbind] (Miles Bader)
> 
> Next time such a jumbo commit is planned, may I ask that the person
> who is about to commit please post a warning here a day or two in
> advance, so that those who don't want to get tons of trivial
> ``changes'' could have an opportunity to disable emacs-diffs mail
> delivery until the commit is over?  I mean, it's not fun to have to
> fetch 22MB of mail with nothing but trivial commits to a CVS branch,
> to say nothing of what it does to the footprint of the Emacs session.

How about simply disabling reporting of branches on that mailing list.
If you're actually interested in a particular branch no doubt something
could be arranged.

-Miles
-- 
"Whatever you do will be insignificant, but it is very important that
 you do it."  Mahatma Gandhi

  reply	other threads:[~2003-10-16  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1A9Zxj-0001tq-7g@monty-python.gnu.org>
2003-10-16  6:27 ` Emacs-diffs Digest, Vol 11, Issue 100 Eli Zaretskii
2003-10-16  8:23   ` Miles Bader [this message]
2003-10-16 11:18     ` Eli Zaretskii
2003-10-16 23:06   ` 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=buobrsha8wb.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --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.
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).