Pharo Issue Tracker - FogBugz (Case [Issue]20182) _Inbox

FogBugz Notification

	James Foster reactivated Case 20182: Extra dot in literal array and assigned it to Everyone: Bug in _Inbox: Not Spam • You are subscribed to this case

I see that a pull request was created for the Github project but I don't understand how that change actually gets into the image. According to https://github.com/pharo-project/pharo, the Github project is a "mirror" of the Pharo packages and is updated FROM the Inria infrastructure. Thus, it is my impression that Pavel's pull request will be ignored.

Sven made a comment that he "patched upstream as well." Does this imply a different procedure?

I see a process at http://pharo.org/contribute-propose-fix that suggests proposed fixes should go to the Pharo 5 Inbox. I also see a Pharo 6 Inbox. I don't see any evidence of a fix for this issue from Sven in either place. Where is the "upstream" patch? When will work start on Pharo 7?

Status changed:
Resolved (Fix Review Needed)

Work Needed

Assigned To changed:
James Foster

Everyone

	Priority: 5 – Fix If Time		Status: Work Needed
	Assigned to: Everyone		Milestone: Later

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want FogBugz notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker

FogBugz (Case [Issue]20182) _Inbox - Extra dot in literal array

FogBugz (Case [Issue]20182) _Inbox - Extra dot in literal array