3 ms·
Can you give me a a terse summary of what "checkout" means that doesn't involve needing to either list or ignore several very different types operations?
by saghm 1mo ago
Can you give me a a terse summary of what "checkout" means that doesn't involve needing to either list or ignore several very different types operations?
- skydhash 1mo agoI would say “align the worktree (or part of it) to a specific state previously saved in the repository.” The repository is a store, you check out the previously saved instance of a file, a group of files, or a subtree. In that regards, switching branches and restoring files is actually the same thing. A commit stores whole files and branches are pointers to commits (which update themeselves).
- saghm 1mo agoThat sounds like an incredibly leaky abstraction to me, and pretty much exactly what I meant by the UX not being very good.
- skydhash 1mo agoWhat is version control to you? For me it’s basically being able to store and retrieve snapshots of code at different instances of time, where each instance has its own significance. Checkout have a very precise meaning in that regards, just like add and commit. Maybe you can explain how is it leaky based on your understanding of version control?