I've definitely set the Bozo Bit on Mercurial. You're more likely to lose data with this than if you just used cp. Absolutely terrible.
-
-
Replying to @cmuratori
@cmuratori You shouldn't really commit something unless you intend to push it soon after. I think this is the root of your problem.1 reply 0 retweets 0 likes -
Replying to @grumpygiant
@grumpygiant I hate that even more. That means you can't backup your work if you're away from the internet, or if it breaks the build.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori AFAIK you can't do that in CVS/SVN/Perforce etc either though right? So it's no worse....2 replies 0 retweets 0 likes -
Replying to @grumpygiant
@grumpygiant You can do it in Perforce, and of course you can do it in cmirror which is what I normally use.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori How do you undo commits in Perforce then?2 replies 0 retweets 0 likes -
Replying to @grumpygiant
@grumpygiant You can "work offline" in Perforce, which allows you to store changelists locally.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@grumpygiant You can then roll those back locally as well, AFAIK (although I don't know that I've done it personally).1 reply 0 retweets 0 likes
@grumpygiant And of course, it also supports shelving changelists, like the "shelve" extension to Mercurial. So you could do that instead.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.