

Debian bug report logs - #1014 , boring messages

-----------------------------------------------------------------------

Message sent to debian-devel@pixar.com:


Subject: Bug#1014: Bug#whatever
Reply-To: grantbow@netcom.com (Grant R. Bowman), debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: grantbow@netcom.com (Grant R. Bowman)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Sat, 17 Jun 1995 06:03:11 GMT
Resent-Message-ID: <debian-bugs-handler.1014.06170554279718@pixar.com>
X-Debian-PR-Package: 
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Sat, 17 Jun 1995 06:03:11 GMT
Received: with rfc822 via encapsulated-mail id 06170554279718;
          Sat, 17 Jun 1995 05:54:27 GMT
Received: from pixar.com by mongo.pixar.com with smtp
        (Smail3.1.28.1 #15) id m0sMqoh-0005z9C; Fri, 16 Jun 95 22:53 PDT
Received: from netcom13.netcom.com by pixar.com with SMTP id AA08849
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Fri, 16 Jun 1995 
22:51:44 -0700
Received: from [192.0.2.1] by netcom13.netcom.com (8.6.12/Netcom)
        id WAA27416; Fri, 16 Jun 1995 22:52:22 -0700
X-Sender: grantbow@netcom13.netcom.com
Message-Id: <v02120d00ac0800275c52@[192.0.2.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 16 Jun 1995 22:51:37 -0700
To: mitchell@mdd.comm.mot.com (Bill Mitchell), debian-bugs@pixar.com
From: grantbow@netcom.com (Grant R. Bowman)

At 7:03 AM 6/16/95, Bill Mitchell wrote:
>Just as note of thanks for your recent bug reports.  A fresh look
>and careful reporting are both welcome.  Most of the rest of us
>have been through so many installs that we never notice most of
>the stuff you've been reporting.

Bill,
        I am glad I can help.  I hope that they are not all duplicates.  
I
have done Software QA for over a year for The Learning Company in 
Fremont,
CA.  It was working on kids games, but it was good paying work and the 
QA
process is the same for most products.  I learned how to create some 
decent
bug reports and what the development process is like.
        Some decisions I know can be purely personal preference and 
simply
based on judgement calls, but I think it's better to over-report and 
throw
bugs out than to not report it at all.  This can take longer, but it 
makes
a better product.  I think the system works best this way, and it helps 
to
have a product you care about (but still be fairly objective, which was
hard at times).  I hope that's the kind of system you have established.
>From my impressions it seems to be.

Cheers,

--
-- Grant R. Bowman                                AdvoTech
-- <grantbow@netcom.com>         Computer and Software Asset Manaagement



-----------------------------------------------------------------------

Message sent:


From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: grantbow@netcom.com (Grant R. Bowman)
Subject: Bug#1014: Acknowledgement (was: Bug#whatever)
In-Reply-To: <v02120d00ac0800275c52@[192.0.2.1]>
References: <v02120d00ac0800275c52@[192.0.2.1]>

Thank you for the problem report you have sent regarding Debian 
GNU/Linux.
This is an automatically generated reply, to let you know your message 
has
been received.  It is being forwarded to the developers' mailing list 
for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1014" or "Re: Bug#1014" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Your message didn't have a Package: line at the start (in the
pseudo-header following the real mail header), or didn't have a
psuedo-header at all.

This makes it much harder for us to categorise and deal with your
problem report; please ensure that you say which package(s) and
version(s) the problem is with next time.  Some time in the future the
problem reports system may start rejecting such messages.

Ian Jackson
(maintainer, debian-bugs)

-----------------------------------------------------------------------

Message sent:


From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: iwj10@cus.cam.ac.uk (Ian Jackson)
In-Reply-To: <m0sN6bK-0000XqZ@chiark.al.cl.cam.ac.uk>
References: <m0sN6bK-0000XqZ@chiark.al.cl.cam.ac.uk> 
<v02120d00ac0800275c52@[192.0.2.1]>
Subject: Bug#1014: marked as done (was: Bug#whatever)

Your message dated Sat, 17 Jun 95 23:44 BST
with message-id <m0sN6bK-0000XqZ@chiark.al.cl.cam.ac.uk>
and subject line Bug#1014: close
has caused the attached bug report to be marked as done.

It is your now responsibility to ensure that the bug report is dealt
with.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(maintainer, debian-bugs)

Received: with rfc822 via encapsulated-mail id 06170554279718;
          Sat, 17 Jun 1995 05:54:27 GMT
From netcom.com!grantbow Fri Jun 16 22:53:11 1995
Return-Path: <grantbow@netcom.com>
Received: from pixar.com by mongo.pixar.com with smtp
        (Smail3.1.28.1 #15) id m0sMqoh-0005z9C; Fri, 16 Jun 95 22:53 PDT
Received: from netcom13.netcom.com by pixar.com with SMTP id AA08849
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Fri, 16 Jun 1995 
22:51:44 -0700
Received: from [192.0.2.1] by netcom13.netcom.com (8.6.12/Netcom)
        id WAA27416; Fri, 16 Jun 1995 22:52:22 -0700
X-Sender: grantbow@netcom13.netcom.com
Message-Id: <v02120d00ac0800275c52@[192.0.2.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 16 Jun 1995 22:51:37 -0700
To: mitchell@mdd.comm.mot.com (Bill Mitchell), debian-bugs@pixar.com
From: grantbow@netcom.com (Grant R. Bowman)
Subject: Re: Bug#whatever

At 7:03 AM 6/16/95, Bill Mitchell wrote:
>Just as note of thanks for your recent bug reports.  A fresh look
>and careful reporting are both welcome.  Most of the rest of us
>have been through so many installs that we never notice most of
>the stuff you've been reporting.

Bill,
        I am glad I can help.  I hope that they are not all duplicates.  
I
have done Software QA for over a year for The Learning Company in 
Fremont,
CA.  It was working on kids games, but it was good paying work and the 
QA
process is the same for most products.  I learned how to create some 
decent
bug reports and what the development process is like.
        Some decisions I know can be purely personal preference and 
simply
based on judgement calls, but I think it's better to over-report and 
throw
bugs out than to not report it at all.  This can take longer, but it 
makes
a better product.  I think the system works best this way, and it helps 
to
have a product you care about (but still be fairly objective, which was
hard at times).  I hope that's the kind of system you have established.
>From my impressions it seems to be.

Cheers,

--
-- Grant R. Bowman                                AdvoTech
-- <grantbow@netcom.com>         Computer and Software Asset Manaagement



-----------------------------------------------------------------------

Message sent:


From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: grantbow@netcom.com (Grant R. Bowman)
Subject: Bug#1014 acknowledged by developer (was: Bug#whatever)
References: <m0sN6bK-0000XqZ@chiark.al.cl.cam.ac.uk> 
<v02120d00ac0800275c52@[192.0.2.1]>
In-Reply-To: <v02120d00ac0800275c52@[192.0.2.1]>

This is an automatic notification regarding your bug report.

Responsibility for it has been taken by one of the developers, namely
iwj10@cus.cam.ac.uk (Ian Jackson).

You should be hearing from them with a substantive response shortly, if
you have not already done so.  If not, please contact them directly,
or email debian-bugs@pixar.com or myself.

Ian Jackson
(maintainer, debian-bugs)

-----------------------------------------------------------------------
Ian Jackson / iwj10@thor.cam.ac.uk , with the debian-bugs tracking
mechanism
This page last modified 06:43:02 GMT Wed 21 Jun