Actually you don't need to save your code to a temporary location. It is enough to opeb the changes dialog before you revert. Having the temporary copy is only useful when you screw up. Lukas On Monday, 9 May 2011, Lukas Renggli <renggli@gmail.com> wrote:
You can't do it automatically from the GUI.
What I do sometimes as a workaround is to commit the package to a temporary location (package cache), restore the old version, and selectively load and commit the changes to the new location.
Lukas
On 9 May 2011 00:35, Nick Chen <nchen.dev@mac.com> wrote:
Hi
When I code, I usually make changes to multiple classes/methods/etc at a time. However, when I commit to Monticello, I would like to organize those changes by breaking them into logical chunks with meaningful commit messages.
Consider the following (trivial) example. Imagine that I would like to commit the change to buildMenuDockOn: in one commit and the change to buildStatusBarWith:on: in another commit. What is the easiest way to achieve this?
http://forum.world.st/file/n3507981/Monticello.png
Other version control systems allow you to selectively stage your changes before committing so I suspect that this should be doable with Monticello.
Thanks!
-- Nick
-- View this message in context: http://forum.world.st/Monticello-How-to-select-unselect-changes-to-be-commit... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
-- Lukas Renggli www.lukas-renggli.ch
-- Lukas Renggli www.lukas-renggli.ch