[Pharo-dev] Cherry Picking Doesn't Dirty MC Packages

I was merging a slice in order to leave out some unwanted changes that got in accidentally. In the merge tool for each of those changes I chose to keep the current version, did the merge, recommitted the slice, and... All the unwanted changes were still there! Apparently, when cherry picking, the packages aren't marked dirty in MC, so they were not saved again with the slice. Only by browsing changes for each package via the working copy browser was I able to get them all marked dirty and commit the new versions. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Cherry-Picking-Doesn-t-Dirty-MC-Packages-tp4822602.htm... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.