Your message dated Tue, 20 Dec 2011 09:24:39 -0400 with message-id <4EF08C97.3070700@debian.org> and subject line Re: Bug#453284: Formulation about followup messages is confusing has caused the Debian Bug report #453284, regarding Formulation about followup messages is confusing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 453284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453284 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Formulation about followup messages is confusing
- From: Bas Wijnen <wijnen@debian.org>
- Date: Wed, 28 Nov 2007 11:40:57 +0100
- Message-id: <20071128104056.GA32698@pcbcn10.phys.rug.nl>
Package: www.debian.org Severity: wishlist Tags: patch On http://www.debian.org/Bugs/Developer, under "Followup messages", there is some confusing text about several bug addresses. I think things would be more clear with a list of addresses and what they do: --------------------------------------------------------------------- The bug tracking system will include the submitter's address and the bug address (nnn@bugs.debian.org) in the Reply-To header after forwarding the bug report. Please note that these are two distinct addresses. If a developer wishes to reply to a bug report they should simply reply to the message, respecting the Reply-To header. This will not close the bug. Do not use the reply to all recipients or followup feature of your mailer unless you intend to edit down the recipients substantially. In particular, see that you don't send followup messages to submit@bugs.debian.org. There are some special addresses which all record the mail in the BTS, but have different addresses to which they forward it. These are: * nnn@bugs.debian.org: To the maintainer and subscribers. This does *not* go to the submitter. * nnn-submitter@bugs.debian.org: To the submitter. This does *not* go to the maintainer. * nnn-maintonly@bugs.debian.org: To the maintainer. This does not go to subscribers, and not even to debian-bugs-dist. * nnn-quiet@bugs.debian.org: This doesn't go anywhere (except to the BTS archive). When several of these addresses are used in combination, the mail is only archived once in the BTS. For example, to send the message to the maintainer and the submitter, you can use To: nnn@bugs.debian.org, nnn-submitter@bugs.debian.org . --------------------------------------------------------------------- Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://pcbcn10.phys.rug.nl/e-mail.htmlAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: debian-l10n-english@lists.debian.org, Bas Wijnen <wijnen@debian.org>, 453284-done@bugs.debian.org, Don Armstrong <don@debian.org>
- Subject: Re: Bug#453284: Formulation about followup messages is confusing
- From: David Prévot <taffit@debian.org>
- Date: Tue, 20 Dec 2011 09:24:39 -0400
- Message-id: <4EF08C97.3070700@debian.org>
- In-reply-to: <[🔎] 20111215224622.GA420@xibalba.demon.co.uk>
- References: <[🔎] 4EEA5ED1.2080309@debian.org> <20111215214705.GA30978__7572.48010854727$1323985709$gmane$org@xibalba.demon.co.uk> <[🔎] 4EEA7488.5080101@debian.org> <[🔎] 20111215224622.GA420@xibalba.demon.co.uk>
Le 15/12/2011 18:46, Justin B Rye a écrit : > The only line I'd tweak now is the last: Thanks Justin, I've just applied the change with your last remarks. Regards DavidAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---