3 ms·
> plus that I can only work on one commit at a time. This is that part of git that bugs me the most! It's totally hostile to the way I prefer to work: one scre
by jeffbee 5y ago
> plus that I can only work on one commit at a time.
This is that part of git that bugs me the most! It's totally hostile to the way I prefer to work: one screen session containing all the editors and shells per change that I am concurrently working on. Git simply cannot do it, unless I clone the entire repo for every change, which is not practical for large projects.
- brigandish 5y agoBecause it’s file based, and that’s obviously behind a lot of the criticism coming from the author of Fossil.
- mlyle 5y ago> simply cannot do it, unless I clone the entire repo for every change Note that you can have multiple working copies from one clone for a few years now. git worktree add <path> <branch>