Subject: | |
From: | |
Reply To: | |
Date: | Tue, 3 Nov 1998 09:07:08 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Newman, Kevin: writes:
> I just went through the painful process of trying to find the MPEJXQ1
> and PXJXQ1 patches for the extended characters in filename patch.
> (needed for g++)
>
> After going through 3 HPRC engineers, checking with Mark Klein, and
> verifying information with a friend in the Patch Management team in
> Atlanta, I have come up with the current patches for this, as of the
> date and time that I send this message!
>
> The current patches for this are:
> MPEKXJ3
> PX2JXQ2
>
> Isn't there an easier way of doing this? The web pages only show the
> current patches, but you cannot search on an old patch from here.
> (unless you pull up every patch and search the page for the old number)
If you search for the original patch ID of MPEJXQ1, the ESC will find MPEKXJ3
because MPEJXQ1 is listed in the huge Supersedes: list.
*MOST UNFORTUNATELY*, the fix text for MPEKXJ3 only talks about the most recent
bug that was fixed, and doesn't mention what was fixed in any of the previous
53 superseded patches. Because the superseded patches are no longer online,
you have no way of knowing what the full impact is going to be of installing
MPEKXJ3. :-(
I strongly urge *ALL* fix text be retained whenever a patch is superseded.
Yes, I know that after 53 supersedes this might add up to a lot of text, but I
really want to know EXACTLY what a patch is fixing or enhancing.
--
Mark Bixby E-mail: [log in to unmask]
Coast Community College Dist. Web: http://www.cccd.edu/~markb/
District Information Services 1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)
|
|
|