3 ms·
There is nothing wrong with using git commands in the terminal. There is also nothing wrong with copying your entire tree to a different directory, diffing, ap
by jwr 5y ago
There is nothing wrong with using git commands in the terminal.
There is also nothing wrong with copying your entire tree to a different directory, diffing, applying patches by hand, and keeping track of what goes where.
Those are different levels of automation for the same fundamental task, but they are all legitimate solutions to the same problem, although you might end up spending more or less time to perform the same fundamental task, depending on the level of automation.
- matheusmoreira 5y ago> There is also nothing wrong with copying your entire tree to a different directory, diffing, applying patches by hand, and keeping track of what goes where. What? There is plenty wrong with that. I've worked with people who did that. There are lots of problems with this approach. It's extremely hard to work with and it only gets harder the more people are involved. At least in git the commits have unique identifiers, everything is hashed and checksummed automatically, branches are properly tracked, etc. I've even worked with non-programmers whose version control was emailing each other files named like: Presentation final final REALLY FINAL (2) (3).ppt It was a hell unlike anything else I had ever experienced before.