Ages ago I suggested a fix to the gcc bug tracking system that would
work for everyone and avoid this stupid situation where everybody's bug
tracking system has to include individual workarounds for every other
bug tracking system: simply make your Bugzilla ignore mails it receives
with the Precede
On Mon, Jan 19, 2004 at 11:32:29PM +0100, Matthias Klose wrote:
> Maybe this was changed with the move of the Debian BTS to the new
> host? Could the same change be made on spohr?
No, my memory is that the mail loops appeared to have stopped ages ago
so I removed the workaround. Certainly the work
Hi,
Maybe this was changed with the move of the Debian BTS to the new
host? Could the same change be made on spohr?
Thanks, Matthias
--- Begin Message ---
--- Additional Comments From dberlin at gcc dot gnu dot org 2004-01-19
21:08 ---
They are auto-replies from debian's bug system.
--- Additional Comments From dhazeghi at yahoo dot com 2004-01-19 21:05
---
I'm not sure what the last 4 messages in the PR are, but they're not
particularly useful to us. Could gcc-bugs be taken off the cc: list for them?
Thanks.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9071
--- Additional Comments From owner at bugs dot debian dot org 2004-01-19
21:10 ---
Subject: Bug#122103: Info received (was Warning for blocks not closed in same
file as opened in)
Thank you for the additional information you have supplied regarding
this problem report. It has been fo
--- Additional Comments From dberlin at gcc dot gnu dot org 2004-01-19
21:08 ---
They are auto-replies from debian's bug system.
I changed the bug reporter so it would stop the mail loop.
I wish the debian guys would stop putting auto-responders as the owners of bugs.
There are quite a
--- Additional Comments From owner at bugs dot debian dot org 2004-01-19
20:51 ---
Subject: Bug#122103: Info received (was Warning for blocks not closed in same
file as opened in)
Thank you for the additional information you have supplied regarding
this problem report. It has been fo
--- Additional Comments From owner at bugs dot debian dot org 2004-01-19
20:39 ---
Subject: Bug#122103: Info received (was Warning for blocks not closed in same
file as opened in)
Thank you for the additional information you have supplied regarding
this problem report. It has been fo
--- Additional Comments From owner at bugs dot debian dot org 2004-01-19
20:21 ---
Subject: Bug#122103: Info received (was Warning for blocks not closed in same
file as opened in)
Thank you for the additional information you have supplied regarding
this problem report. It has been fo
--- Additional Comments From owner at bugs dot debian dot org 2004-01-19
20:08 ---
Subject: Bug#122103: Info received (was Warning for blocks not closed in same
file as opened in)
Thank you for the additional information you have supplied regarding
this problem report. It has been fo
--- Additional Comments From owner at bugs dot debian dot org 2004-01-19
19:51 ---
Subject: Bug#122103: Info received (was Warning for blocks not closed in same
file as opened in)
Thank you for the additional information you have supplied regarding
this problem report. It has been fo
--
What|Removed |Added
Component|c |preprocessor
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9071
--- You are receiving this mail because: --
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9071
pinskia at physics dot uc dot edu changed:
What|Removed |Added
13 matches
Mail list logo
