Re: Learnin' some git. Was: RE: Is this the future of technical writing?

[Tony Chung <tonyc -at- tonychung -dot- ca>]

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 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