3 ms·
A couple obvious questions: - Is it possible to design a Git-like VCS with only two or three "places" instead of five? - What would be the downsides of such a
by cousin_it 13y ago
A couple obvious questions:
- Is it possible to design a Git-like VCS with only two or three "places" instead of five?
- What would be the downsides of such a system?
- deleted 13y ago[deleted]
- TylerE 13y agoSure, and not many. That's more or less Mercurial.
- rakoo 13y agoThe remote repo, local repo and working directory are the strict minimum to work efficiently with git. To be fair, I barely use the stash, and if you're ok with that you can always use `git commit -am`, which commits every changes without going through the index. Lots of people do it, and I believe this is acutally how most people start with git. It's an error to fear the number of "Places". They are here to help you, not to prevent you from working. If you don't need them, don't use them: if you're working alone you don't need a remote repository. You can always add this place in your places set at a later time. If you don't need the stash, don't use it. The approach of the post is top-down, which is an enormous error: git is such a beast that it's impossible to grasp all its mechanics before diving in it. You should use a bottom-up approach, start with the simple tools, and gradually go up _as you need it_. Then, you start learning about `git rebase -i`, and you can't make without an index... But that comes at a later time.