Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id o2UE0wUq011677 for ; Tue, 30 Mar 2010 16:01:00 +0200 Received: (qmail 32425 invoked by alias); 30 Mar 2010 14:00:53 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 30 Mar 2010 14:00:51 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx118) with SMTP; 30 Mar 2010 16:00:51 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id o2UDwakX003994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Mar 2010 15:58:36 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id o2TM26qg005642; Tue, 30 Mar 2010 15:58:35 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 387540 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 30 Mar 2010 15:58:35 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id o2UDmY0I019972 for ; Tue, 30 Mar 2010 15:48:34 +0200 Received: from g5t0007.atlanta.hp.com (g5t0007.atlanta.hp.com [15.192.0.44]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id o2UDmJAw020859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 30 Mar 2010 15:48:23 +0200 Received: from G5W0603.americas.hpqcorp.net (g5w0603.americas.hpqcorp.net [16.228.9.186]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g5t0007.atlanta.hp.com (Postfix) with ESMTPS id 9F0A8140DE for ; Tue, 30 Mar 2010 10:10:32 +0000 (UTC) Received: from G4W1852.americas.hpqcorp.net (16.234.97.230) by G5W0603.americas.hpqcorp.net (16.228.9.186) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 30 Mar 2010 10:09:11 +0000 Received: from GVW1086EXB.americas.hpqcorp.net ([16.234.42.2]) by G4W1852.americas.hpqcorp.net ([16.234.97.230]) with mapi; Tue, 30 Mar 2010 10:09:11 +0000 Thread-Topic: replying to a LaTeX bug record Thread-Index: AcrPq+GBLU+/FiywQGal/A7lqdtofgARKo8A References: <20100330015247.GA24070@oberdiek.my-fqdn.de> Accept-Language: de-DE, en-US Content-Language: en-US acceptlanguage: de-DE, en-US Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id o2UDmZ0I019973 Message-ID: <2696D01678E2A74CB37830D58DFAA15C7383D67BCA@GVW1086EXB.americas.hpqcorp.net> Date: Tue, 30 Mar 2010 10:06:18 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: "Mittelbach, Frank" Subject: replying to a LaTeX bug record To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <20100330015247.GA24070@oberdiek.my-fqdn.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p4WX0t+AtsdWzrXATe7U7iyEYsVEub6UEScnitTuLsF1dwROLenO8vOmwvdy pgJ/SUsFNrCZZib4xGIRhKVI5/3XJCDlTO3AUhsOBsdGA7aE8f9QyJnx4GXo3kvaK52rz5wLFjTv haXng==V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6327 Hallo Heiko, I'm sorry for the trouble with the gnats system it is unfortunately not the best possible interface. You actually managed to reach the bug database each time, what you didn't manage was to reach it in a way that your mail shows up on the web. Here are the rules (as far as I remember them - if mistaken, I'm sure Rainer will correct me) To answer a bug entry: - you send mail to latex-bugs@latex-project.org - to avoid generating a new bug entry this way you need to use a subject line that contains / at the beginning (if think stuff like Re: etc is possible - you can have additional text in the subject and it doesn't have to match the original bug synopsis - if you do the above the entry will end up in the database but it will not show up on the web and it will be distributed internally but not back to the original poster (that's the way gants works) - if you want it to appear on the web you need to explicitly include the original poster on CC or To: And that actually is the catch: with so much misuse and email adress harvesting the email addresses are no longer shown and so there isn't really any way for you to do that Not sure what the best way is, perhaps in a case like this, open a new bug report and crossref though that isn't really a good solution either. What I can do is to take your reply and add it again with cc to the originator s othat he/she gets it and it shows on the web (not from here but tonight) Frank -----Original Message----- From: Mailing list for the LaTeX3 project [mailto:LATEX-L@LISTSERV.UNI-HEIDELBERG.DE] On Behalf Of Heiko Oberdiek Sent: Tuesday, March 30, 2010 3:53 AM To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE Subject: Re: latex/3540: \DoNotIndex{\#,\$,\%,\^,\_,\~,\ ,\&,\{,\}} Hello, this is an answer to an old LaTeX bug (see LaTeX bug database). Unhappily I can't write an answer to the LaTeX bug system. After three failed tries I have to use this list for that. Please update the help text in the database: * How to answer to a bug entry? * Which email address(es)? Probably: latex-bugs@latex-project.org Anything else? How is the bug reporter is notified, if the answering person is different? * From address? Is any address allowed or it is limited to the bug reporter and authorisized people (LaTeX team)? * Subject? I have seen Re: / and Re: /: * Are there delays in the processing of mails send to the bug database regarding answers (cronjob, moderation, ...)?