Issue 7428 in pharo: Either remove or run MCWorkingCopyBrowser>>checkForNewerVersions

Status: Accepted
Owner: [hidden email]
Labels: Type-Cleanup Target-Monticello Milestone-3.0 Difficulty-Easy

New issue 7428 by [hidden email]: Either remove or run  
MCWorkingCopyBrowser>>checkForNewerVersions
http://code.google.com/p/pharo/issues/detail?id=7428

We have this method without senders:

MCWorkingCopyBrowser>>
checkForNewerVersions
        | newer |
        newer := workingCopy possiblyNewerVersionsIn: self repository.
        ^ newer isEmpty or: [
                self confirm: 'CAUTION! These versions in the repository may be newer:',
                        String cr, (newer asString truncateWithElipsisTo: 300), String cr,
                        'Do you really want to save this version?'].

In Squeak (4.3), they execute it from MCWorkingCopyBrowser>>saveVersion.

It prevents accidental commits when there are newer (unmerged) versions in  
the repository.

We could either remove it or add it the #saveVersion. This adds an extra  
overhead to each time one saves a version.




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

Comment #1 on issue 7428 by [hidden email]: Either remove or run  
MCWorkingCopyBrowser>>checkForNewerVersions
http://code.google.com/p/pharo/issues/detail?id=7428

They have a preference (checked in Sq 4.3).


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