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: John G <john -at- garisons -dot- com>
To: Tony Chung <tonyc -at- tonychung -dot- ca>
Date: Wed, 29 Oct 2014 09:14:15 -0400

Git is difficult. I use it to read and comment on scenarios and to
edit/approve text strings in the UI, and I quickly determined that I only
need a small subset of commands to do the things I need to do. But I have
to be very precise in how I do them. I have a cheat sheet that I follow
religiously.

Tech writers may not be the best audience to get feedback from on this
topic as they are, for the most part, far from the mainstream of actual
Git users.

My 2Â,

JG

On Wed, Oct 29, 2014 at 3:29 AM, Tony Chung <tonyc -at- tonychung -dot- ca> wrote:

> 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
> reference card.
>
> -Tony
>
> 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
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as vwritert -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
> http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


References:
Learnin' some git. Was: RE: Is this the future of technical writing?: From: Sweet, Gregory (HEALTH)
Re: Learnin' some git. Was: RE: Is this the future of technical writing?: From: Tony Chung

Previous by Author: Re: Is this the future of technical writing?
Next by Author: Re: keeping the page count down?
Previous by Thread: Re: Learnin' some git. Was: RE: Is this the future of technical writing?
Next by Thread: Documentation collaboration - best practices and tools used?


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads