I use Git and have a work flow similar to what you are describing. My git commits are usually frequent, focused and sometimes staged. But I also manually copy the entire project folder or repository at various points in time and put it in a manual backup or history folder. I usually keep the last 20 or more of these manual backups.
This frees me up for doing what ever crazy thing I want in the active git repository. If it starts going south I can just throw it all away (along with the Xcode project specific "DerivedData" directory), pull out a prior "version" from the manual backup directory and start fresh again. The whole process takes about a minute and has been bullet proof. I still use Git for reviewing history, managing branches, merging changes from one branch to another, etc., but this modified workflow has made my day to day development go much faster. --Richard Somers On Nov 29, 2012, at 1:02 PM, Yi Lin <[email protected]> wrote: > I do use Git, and take advantaging of its staging abilities. But sometimes, > I want to do some quick experiments and want to get back to a previous > state. Kind of like undoing with Command-Z except it involves multiple > files. > > Yes, theoretically, Git can do all that. But are you telling me people who > use Git never invoke undo? Snapshot would work more like named, multi-file > undo for me, rather than as VC. > > But still, I just want Snapshot to work. Right now it doesn't, except on > the simplest of projects. _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
