Smalltalk
›
Pharo
›
Pharo Issue Tracker
Search
everywhere
only in this topic
Advanced Search
Manuscript (Case [Issue]21570) Kernel - The system should not decide if a class is abstract or not
‹
Previous Topic
Next Topic
›
Classic
List
Threaded
♦
♦
Locked
1 message
Pharo Issue Tracker
Reply
|
Threaded
Open this post in threaded view
♦
♦
|
Manuscript (Case [Issue]21570) Kernel - The system should not decide if a class is abstract or not
Manuscript Notification
Guillermo Polito
resolved
Case 21570
: The system should not decide if a class is abstract or not
and assigned it to
Guillermo Polito
:
Bug
in
Kernel: 1. Pharo Image • You are subscribed to this case
Status
changed:
Resolved (Fix Review Needed)
Resolved (Fix Integrated)
Priority
: 3 – Must Fix
Status
: Resolved (Fix Integrated)
Assigned to
: Guillermo Polito
Milestone
: Later
Go to Case
No longer need updates?
Unsubscribe from this case.
Don't want Manuscript notifications anymore?
Update your preferences.
A Manuscript case was Resolved (Fix Integrated) and assigned to Guillermo Polito by Guillermo Polito. Case ID: 21570 Title: The system should not decide if a class is abstract or not Status: Resolved (Fix Integrated) Category: Bug Project: Kernel Area: 1. Pharo Image Priority: 3 - Must Fix Milestone: Later Assigned To: Guillermo Polito URL: https://pharo.manuscript.com/f/cases/21570 Changes: Status changed from 'Resolved (Fix Review Needed)' to 'Resolved (Fix Integrated)'. You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.manuscript.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=21570) from this case.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker
Free forum by Nabble
Edit this page