Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
Subject: Re: Gnus's message-unique-id breaks in Emacs 22
Date: Sun, 10 Jul 2005 07:34:45 +0900	[thread overview]
Message-ID: <87k6jzham2.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <1116662633.315914.45990@z14g2000cwz.googlegroups.com>

"silent.wave" <silent.wave@gmail.com> writes:
> The Elisp function message-unique-id in message.el breaks in Emacs 22
> Where do I submit the bug fix?

For gnus-specific bugs, ding@gnus.org is a possibility (there's a
bug-reporting address for gnus, but it lately seems to be of dubious
reliability); I've no idea what the recommended address is for the emacs
CVS version, but emacs-devel or emacs-pretest-bug (both @gnu.org) would
work.

-Miles
-- 
Any man who is a triangle, has thee right, when in Cartesian Space, to
have angles, which when summed, come to know more, nor no less, than
nine score degrees, should he so wish.  [TEMPLE OV THEE LEMUR]


      reply	other threads:[~2005-07-09 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21  8:03 silent.wave
2005-07-09 22:34 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k6jzham2.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.
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).