| Summary: | Minor typo in error message when invalid source information is given | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Ben Chen <chenbs> | ||||
| Component: | TPTP | Assignee: | Paul Slauenwhite <paulslau> | ||||
| Status: | CLOSED FIXED | QA Contact: | Kathy Chan <kathy> | ||||
| Severity: | minor | ||||||
| Priority: | P2 | CC: | jcayne, paulslau | ||||
| Version: | unspecified | Flags: | paulslau:
pmc_approved?
(oec) paulslau: pmc_approved? (ernest) kathy: pmc_approved+ paulslau: pmc_approved? (paulslau) paulslau: pmc_approved? (ewchan) paulslau: pmc_approved? (jgwest) jcayne: review+ |
||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ben Chen
Created attachment 170242 [details]
Patch.
Joel, please review this small patch. Patch looks good. Requesting PMC approval for TPTP 4.7.0: 1. Explain why you believe this is a stop-ship defect. How does the defect manifest itself, and how will users of TPTP / consuming products be affected if the defect is not fixed? Minor typo in a properties file. 2. Is there a work-around? If so, why do you believe the work-around is insufficient? No. 3. Is this a regression or API breakage? Explain. N/A 4. Does this require new API? No. 5. Who performed the code review? Joel Cayne 6. Is there a test case attached to the bugzilla record? Covered by existing test case(s). 7. What is the nature of the fix? What is the scope of the fix? What is the risk associated with this fix? Fix the minor typo in a properties file. 8. Is this fix related to any standards that TPTP adheres to? If so, who has validated that the fix continues to adhere to the standard? No. The attached patch is checked in to CVS (HEAD). verified in TPTP-4.7.0-201006011014 (In reply to comment #6) > verified in TPTP-4.7.0-201006011014 Closing |