3 ms·
Previously: <https://news.ycombinator.com/item?id=40558094#40568509 https://news.ycombinator.com/item?id=40558094#40568509> The recommended approach in the art
by cxr 2y ago
Previously: <https://news.ycombinator.com/item?id=40558094#40568509 https://news.ycombinator.com/item?id=40558094#40568509>
The recommended approach in the article is not a good one, though. What you'll end up with is worse than just running unzip by hand—so just do that instead. Programmers thinking that they need Git itself (or some plugin for it) to support the file format is just a weird mental block, anyway.
Unzip the files. Check in the necessary changes. It's not hard or a hard concept to grasp.
- dotancohen 2y ago> Programmers thinking that they need Git itself (or some plugin for it) to support the file format is just a weird mental block Git supporting the file format has several advantages. For one thing, changing a single word in a 37 MiB file won't add 37 MiB to the repo. For another, one could use the Git log to review the changes across commits and branches.