Your message dated Tue, 13 Feb 2007 08:16:34 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#234058: gdm: Capslock warning on sparc warns for numlock,
not capslock
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt wit
#
# bts-link upstream status pull for source package xserver-xorg-video-mga
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #405998
# * https://bugs.freedesktop.org/show_bug.cgi?id=9761
# * remote status changed: (?)
#
# bts-link upstream status pull for source package libx11
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #133348
# * https://bugs.freedesktop.org/show_bug.cgi?id=9828
# * remote status changed: (?) -> NEW
usertags
Your message dated Tue, 13 Feb 2007 08:12:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#160841: xserver-xfree86: [tdfx] exhausts virtual memory
and arouses Linux OOM killer when changing video modes on Voodoo5 rev 1
has caused the attached Bug report to be marked as done.
This
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> tags 301450 + wontfix
Bug#301450: xserver-xfree86: Can't open apm_bios device when using devfs device
naming rules
There were no tags set.
Tags added: wontfix
>
End of message, stop
debian/changelog | 12 ++--
debian/control |5 +++--
2 files changed, 13 insertions(+), 4 deletions(-)
New commits:
commit b453c54793bf98b62f0e2189fa2bc4c8f11ac3fa
Author: Julien Cristau <[EMAIL PROTECTED]>
Date: Tue Feb 13 08:24:24 2007 +0100
Make x11-common conflict with
> "Brice" == Brice Goglin <[EMAIL PROTECTED]> writes:
Brice> Hi Eric, Did you have a chance to try to reproduce this
Brice> bug?
No; I no longer use that particular video card.
--
I ... don't want programming to be "really interesting" any more than
I want my toaster to be "really i
#
# bts-link upstream status pull for source package libxkbfile
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #407189
# * https://bugs.freedesktop.org/show_bug.cgi?id=9796
# * remote status changed: (?) -> NEW
usert
FYI: The status of the libx11 source package
in Debian's testing distribution has changed.
Previous version: 2:1.0.3-4
Current version: 2:1.0.3-5
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
FYI: The status of the xterm source package
in Debian's testing distribution has changed.
Previous version: 222-1etch1
Current version: 222-1etch2
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
FYI: The status of the xserver-xorg-video-i810 source package
in Debian's testing distribution has changed.
Previous version: 2:1.7.2-3
Current version: 2:1.7.2-4
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for mo
Brice,
Hey, thanks for the reply? as I haven't been getting any responses from
reportbug lately and haven't had a lot of time to investigate it. I don't
remember which system I was on when I sent this, but haven't seen
it in a while--except if a game gets aborted by `killall -9 badgame'.
Take c
Hi Eric,
Did you have a chance to try to reproduce this bug?
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Simon,
Did you have a chance to try to reproduce this bug?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Sven,
Did you have a chance to look at this bug as you said you would about 3
weeks ago?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Christoph,
Did you have a chance to try to reproduce this bug with your old board?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Mark,
Did you have a chance to try to reproduce this bug?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, but some people said it's fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, but some people said it's fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Tue, 13 Feb 2007 00:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, but some people said it's fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, but some people said it's fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Tue, 13 Feb 2007 00:52:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, but some people said it's fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Your message dated Tue, 13 Feb 2007 00:51:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout
has caused the attached Bug report 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 reo
Package: x11-common
Version: 1:7.1.0-11
Severity: serious
Please add opera (<< 9.10-20061214.6) to the list of packages conflicted
with by x11-common for the /usr/X11R6/bin transition. It's been brought to
my attention on IRC that this version of the third-party opera package fixes
the binary pat
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, closing
has caused the attached Bug report 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 responsibili
1 - 100 of 173 matches
Mail list logo
