HP3000-L Archives

November 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Paveza, Gary" <[log in to unmask]>
Reply To:
Paveza, Gary
Date:
Wed, 15 Nov 2000 11:22:43 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
But this begs the question, should the customer have to go to these lengths
to get a bug report to HP?  One would think that HP would make it as easy as
possible to provide this information.

-------------------------------------------------------------
Gary L. Paveza, Jr.
Technical Services Manager
(302) 761-3173 - voice
(877) 720-2970 - pager

        -----Original Message-----
        From:   Mark Bixby [SMTP:[log in to unmask]]
        Sent:   Wednesday, November 15, 2000 11:20 AM
        To:     [log in to unmask]
        Subject:        Re: [HP3000-L] HP ITRC : went from bad to worse

        Sletten Kenneth W KPWA wrote:
        > >    9) Shamefully inadequate bug text submission
        > >
        > >       Bug text is limited to 60 lines of 80 characters ...
        >
        > ... making it difficult when you have, say, 800+ lines of
pertinent
        > data available on your monitor....  another problem that would
        > (I sure hope) be solved by email bug reports...

        When I was a customer, I worked around this serious limitation by
putting any
        voluminous pertinent data into a web page (hosted on Apache on MPE
of course)
        and then submitting my URL as one of those 60 lines of ITRC call
text.

        - Mark B.

ATOM RSS1 RSS2