HP3000-L Archives

February 2001, Week 1

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:
Bill Cadier <[log in to unmask]>
Reply To:
Bill Cadier <[log in to unmask]>
Date:
Wed, 7 Feb 2001 19:16:17 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Eben wrote:

> I have a patch tape from HP for these patches:
>
> ATCLX76 (A)
> QUELXD6 (C)
> SQLLX50 (C)
> TIXLXE5 (A)
>
> I'm just curious... what does the (A) and (C) represent?
>

When a patch is started it is usually started for each supported release so
patch MPExxyy (A) would be for 6.0 and MPExxyy (B) would be for
6.5 for example. Although sometimes the person doing the 'setting up'
might ask for the 6.5 patch first and the 6.0 version later so you can't
tell just from the letter what it is .

If a patch is pulled and reworked we roll the version, so A becomes B.
This is not a common occurance. If it occurs it is done while the patch is
in the 'beta test' phase.

And finally, in the OS (MPE prefix patches that I'm likely to do) we
create patches as 'site specific' while we ensure they work. This prevents
the source files used to create them from being inadvertently picked up in
some other patch. It also means that when the patch is blessed as good
we need to merge the changes back into the current source files and
recompile so we roll the version in this case to to avoid any confusion
about who's got what. A bit more work but cleaner in the long run.

Hope that answers your question!

Bill
HP/CSY
reply to: [log in to unmask]

ATOM RSS1 RSS2