edit-article

Article Description: ] ARTICLE describing the 'git' version control software

Chapter ID/Name:

Status: Write Writing Written

Add Photo:

Owner ID:

Content: use HTML Edit Content <h1 style="text-align: center;">git</h1> <h2>[WHAT]</h2> <ol> <li><strong>]&nbsp;git</strong></li> <ol> <li>]&nbsp;an open source version control system,</li> <li>] has become the &nbsp;defacto standard for open source software development and is increasingly being used for enterprise s/w dev</li> <li>] originally developed by <span style="text-decoration: underline;">Linus Torvalds</span> for managing the Linux os project, not developed as a Source Control Management(SCM) app but more as a filesystem</li> <li>]</li> </ol> <li><strong>] git bash</strong></li> <ol> <li>] command line scripting environment for working with git projects</li> </ol> <li><strong>] git gui</strong></li> <ol> <li>] native graphical UI for working with git projects, subset of all git commands available in,</li> <li>] (third party) gui clients are also available for working with git projects, choose your poison</li> </ol></ol> <h2>[WHY]</h2> <ol> <li><strong>]&nbsp;a "distributed" version control system </strong>- for source code management(SCM)</li> <ol> <li>] primarily used in software development projects,</li> <li>] to control/monitor/document changes to a project,</li> <li>] becomes essential on a larger project where multiple developers will work on the same project&nbsp;&nbsp;</li> </ol> <li><strong>] free</strong></li> <ol> <li>]</li> </ol> <li><strong>] open source</strong></li> <ol> <li>] licenced under gnu general public v2</li> </ol> <li><strong>] local </strong></li> <ol> <li>] FAST - Every Git <a title="Working directory" href="http://en.wikipedia.org/wiki/Working_directory">working directory</a> is a full-fledged <a title="Repository (version control)" href="http://en.wikipedia.org/wiki/Repository_(version_control)">repository</a> with complete history and full version tracking capabilities, not dependent on network access or a central server</li> </ol></ol> <h2>[WHY NOT]</h2> <ol> <li><strong>] git has been accused of being </strong></li> <ol> <li>] hard to learn</li> <li>] confusing / overly complicated</li> <li>]</li> </ol> <li><strong>] git alternatives</strong></li> <ol> <li>]</li> </ol></ol> <h2>[WHERE - ???]</h2> <ol> <li>] git bash</li> <li>] git gui</li> <li>] ...</li> </ol> <h2>[WHEN]</h2> <ol> <li>]</li> </ol> <h2>[EXAMPLE]</h2> <ol> <li>]</li> </ol> <h2>[HOW-TO]</h2> <ol> <li><strong>] Y step-by-step</strong></li> <ol> <li>] <a href="/view/steps?id=41" target="_blank">git installation on windows</a>&nbsp;-</li> <li>] <a href="/view/steps?id=42" target="_blank">git bash configuration</a> -</li> </ol></ol> <h2>[REFERENCE]</h2> <ol> <li><strong>] BOOK - </strong><a href="/view/chapters?id=263" target="_blank"><strong>git started</strong></a><ol> <li>] #&nbsp;2459 - <a href="/view/article?id=2459" target="_blank">table of contents</a> - a guide to learning git for noobs</li> </ol></li> <li><strong>] project#035-learning-git</strong></li> <ol> <li>] # <a href="/view/taskgroups?id=130" target="_blank">plan</a> - ] creating the git started guide, &nbsp;] # 4076&nbsp;<a href="/view/article?id=4076" target="_blank">overview</a></li> <li>] # <a href="/view/taskgroups?id=131" target="_blank">doc</a> ] # <a href="/view/tasks?id=326" target="_blank">review</a></li> </ol></ol> <h1 style="text-align: center;">&nbsp;</h1>