3 ms·
No daemon, it happens 'whenever you run a command'. > Commands snapshot the working copy before they start, then the update the repo, and then the working copy
by OJFord 3y ago
No daemon, it happens 'whenever you run a command'.
> Commands snapshot the working copy before they start, then the update the repo, and then the working copy is updated (if the working-copy commit was modified). Almost all commands (even checkout!) operate on the commits in the repo, leaving the common functionality of snapshotting and updating of the working copy to centralized code.
- systems 3y agoso commit is a side effect, not an explicit action weird choice, isnt explicit always better than implicit