3 ms·
> If you're say, changing an API, You obviously take the snapshot before. No different from the more over-engineered approaches. >> How does "bisect" know whe
by nearestneighbor 16y ago
> If you're say, changing an API,
You obviously take the snapshot before. No different from the more over-engineered approaches.
>> How does "bisect" know where the boundaries are?
> Clever algorithms.
Really?! You change two methods in a class, and "bisect" knows how to undo only one? No, you have to spoon-feed it, "staging" your changes (I did use GitX for a day). So it's not as simple as taking snapshots after all, is it?
Edit: typo, formatting
- blasdel 16y agoYes, git asks that you make your commits actually make sense, instead of "oh I'm about to leave, better check in all the unrelated shit I did today" Sounds like you'd fit in just fine with ClearCase users.
- nearestneighbor 16y agoMaybe you should have instead posted your retort when someone claimed that Git's commits are as simple as taking tarball snapshots?