Smalltalk › Pharo › Pharo Issue Tracker

Manuscript (Case [Issue]22249) Sources and Changes - Epicea should not propose to recover lost changes if there is no ombu file in pharo-local

_‹ Previous Topic Next Topic _›

Classic

List

1 message

Options

Pharo Issue Tracker

Manuscript (Case [Issue]22249) Sources and Changes - Epicea should not propose to recover lost changes if there is no ombu file in pharo-local

Manuscript Notification

	Martin Dias resolved Case 22249: Epicea should not propose to recover lost changes if there is no ombu file in pharo-local and assigned it to CyrilFerlicot: Enhancement in Sources and Changes: 1. Pharo Image • You are subscribed to this case

Status changed:
Work Needed

Resolved (Duplicate)

Assigned To changed:
Everyone

CyrilFerlicot

Duplicate Of changed:
None

Case 21708

	Priority: 4 – Would be nice		Status: Resolved (Duplicate)
	Assigned to: CyrilFerlicot		Milestone: Later

No longer need updates? Unsubscribe from this case.

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

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