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:Robert Lauriston <robert -at- lauriston -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 10 Nov 2014 10:41:31 -0800
Functionally, for managing doc files, I find Git similar to CVS, SVN,
P4, and VSS. The cheat sheet I wrote for the tasks I perform regularly
has only seven commands (clone, checkout, pull, rm, add, commit, push)
in a few different permutations.
I think every revision control system I've used has had a significant
learning curve. There's always some command you expect to have that's
missing, or the workflow is backwards from what you're used to.
On Mon, Nov 10, 2014 at 10:26 AM, Shawn <shawn -at- cohodata -dot- com> wrote:
> To make matters somewhat more challenging, every company implements git in
> a slightly different manner. It is a very flexible tool that way.
> Even thought I am very technical (spent years as a Network Admin - Novell,
> Windows, and Linux servers), I have not yet fully embraced git for
> documentation in my current company. I find git`s CLI (via Cygwin terminal)
> very cryptic and not quite suitable for documentation (IMO). To date, I've
> been using it only as a backup application. Rather unnecessary because I
> prefer and depend on my personal 3.5" HDD for off-site backup and my
> Dropbox sync for instant cloud recovery.
> Until Flare keeps their promise and adds in git support, I will likely not
> use git for any important role.
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l