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.
Re: Learnin' some git. Was: RE: Is this the future of technical writing?
Subject:Re: Learnin' some git. Was: RE: Is this the future of technical writing? From:Tony Chung <tonyc -at- tonychung -dot- ca> To:"Sweet, Gregory (HEALTH)" <gregory -dot- sweet -at- health -dot- ny -dot- gov> Date:Wed, 29 Oct 2014 00:29:32 -0700
Thanks Greg! I've been using Git for a few projects this past year to
maintain a consistent code base between my work and home computers and a
Bitbucket repo. There was some confusion at the beginning where each
computer couldn't find the most recent source--because Git is designed as a
distributed repo, not client server with locks.
You really need to understand branching and merging in order to truly get
Git to bow down to you.
I look forward to reading the same book and downloading your quick
On Tuesday, October 28, 2014, Sweet, Gregory (HEALTH) <
gregory -dot- sweet -at- health -dot- ny -dot- gov> wrote:
> Git does come with its own new unique vocabulary. And until you come to
> grips with what a push, pull, fetch, merge, remote, branch, head. etc. are
> you are not going to be successful...
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l