Smalltalk
›
Pharo
›
Pharo Issue Tracker
Search
everywhere
only in this topic
Advanced Search
Manuscript (Case [Issue]22319) Refactoring - Extracting an already existing method should not raise an error!
‹
Previous Topic
Next Topic
›
Classic
List
Threaded
♦
♦
Locked
1 message
Pharo Issue Tracker
Reply
|
Threaded
Open this post in threaded view
♦
♦
|
Manuscript (Case [Issue]22319) Refactoring - Extracting an already existing method should not raise an error!
Manuscript Notification
Marcus Denker
resolved
Case 22319
: Extracting an already existing method should not raise an error!
and assigned it to
Stephane Ducasse
:
Bug
in
Refactoring: 1. Pharo Image • You are subscribed to this case
Status
changed:
Resolved (Fix Review Needed)
Resolved (Fixed upstream)
Priority
: 3 – Must Fix
Status
: Resolved (Fixed upstream)
Assigned to
: Stephane Ducasse
Milestone
: Pharo7.0
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 (Fixed upstream) and assigned to Stephane Ducasse by Marcus Denker. Case ID: 22319 Title: Extracting an already existing method should not raise an error! Status: Resolved (Fixed upstream) Category: Bug Project: Refactoring Area: 1. Pharo Image Priority: 3 - Must Fix Milestone: Pharo7.0: 9/2/2018 (Past) Assigned To: Stephane Ducasse URL: https://pharo.manuscript.com/f/cases/22319 Changes: Status changed from 'Resolved (Fix Review Needed)' to 'Resolved (Fixed upstream)'. 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=22319) 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