4 ms·
500 pages (excuse me, 501) to document a source control tool. Something went very wrong here early on. But, lacking a time machine and a handgun, it's clearly
by CamperBob2 2y ago
500 pages (excuse me, 501) to document a source control tool.
Something went very wrong here early on. But, lacking a time machine and a handgun, it's clearly unfixable.
- Tijdreiziger 2y agoThe first 6-7 chapters should teach you more than most Git users know (myself included, suppose I might be due a re-read!).
- skydhash 2y agoWhich you can read easily in a week or two without much effort for something that is currently de facto for software development. The Emacs Manual has ~700 pages.
- metabagel 2y agoThis seems wildly optimistic.
- datadrivenangel 2y ago1, Source control can get very gnarly when you have multiple editors on a codebase, and 2, good and comprehensive documentation for software is often many times longer than the software it documents. Man pages are a lot longer than -h