unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Subject: Re: `emacs-diffs@gnu.org' local delivery failed
Date: 18 Aug 2002 08:40:21 +0900	[thread overview]
Message-ID: <87r8gx12ca.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: 87u1lt12jd.fsf@tc-1-100.kawasaki.gol.ne.jp

BTW, I got a similar bounce for the address `emacs-commit@gnu.org' (for
but a different checkin!)...

I did a bunch of checkins at about the same time, but only those two
error messages, so I guess it's a transient failure of some sort; was
it just someone screwing around with the mailing lists?

-Miles

      reply	other threads:[~2002-08-17 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-17 23:36 `emacs-diffs@gnu.org' local delivery failed Miles Bader
2002-08-17 23:40 ` Miles Bader [this message]

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=87r8gx12ca.fsf@tc-1-100.kawasaki.gol.ne.jp \
    --to=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).