TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Git for Tech Pubs [was FW: L@@king for recommendations for a doc source-file management system....]
Subject:Git for Tech Pubs [was FW: L@@king for recommendations for a doc source-file management system....] From:"Janoff, Steven" <Steven -dot- Janoff -at- hologic -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 20 Nov 2018 23:10:31 +0000
Picking up on this thread from Sept.
Tony, you'd confirmed what I'd thought about Git causing bloat.
What I wonder about though is that Git seems to be gaining ground in the Tech Comm industry.
I'm sure it's great for API/SDK documents where there's heavy text and few images or other binary files.
Are we just stuck with it as is, if we have lots of binary files?
Thanks,
Steve
On Wednesday, September 12, 2018 6:49 AM, Tony Chung wrote:
Git isnât recommended for binary files because its benefit of storing changes only is negated, and bloats the repo for all users. Most FM and Word shops I know use SVN or VSS.
-Tony
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com