Gnus development mailing list
 help / color / mirror / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: ding@gnus.org, 21071@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: bug#21071: Gnus message flags must be set before expiration, not afterwards
Date: Wed, 15 Jul 2015 20:21:43 -0400	[thread overview]
Message-ID: <twa8ux7y08.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87mvyx2c20.fsf@vostro.rath.org> (Nikolaus Rath's message of "Wed, 15 Jul 2015 17:14:47 -0700")


You don't need to x-debbugs-cc every bug report you make to emacs-devel
and ding@gnus.org, thus sending it to 3 (including gnus-bug) separate
mailing lists. Just the bug list is fine.



  reply	other threads:[~2015-07-16  0:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  0:14 Nikolaus Rath
2015-07-16  0:21 ` Glenn Morris [this message]
2015-07-16  8:49   ` Steinar Bang
     [not found]   ` <87fv4p2b9n.fsf@vostro.rath.org>
2015-10-06 21:03     ` Nikolaus Rath
2017-01-26 19:43       ` Lars Ingebrigtsen
2019-09-27 16:04       ` Lars Ingebrigtsen

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=twa8ux7y08.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=21071@debbugs.gnu.org \
    --cc=Nikolaus@rath.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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).