githttps://www.linuxjournal.com/tag/git
enBrent Laster's Professional Git (Wrox)https://www.linuxjournal.com/content/brent-lasters-professional-git-wrox
<div data-history-node-id="1339296" class="layout layout--onecol">
<div class="layout__region layout__region--content">
<div class="field field--name-field-node-image field--type-image field--label-hidden field--item"> <img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/12131f7.jpg" width="283" height="356" alt="" typeof="foaf:Image" class="img-responsive" /></div>
<div class="field field--name-node-author field--type-ds field--label-hidden field--item">by <a title="View user profile." href="https://www.linuxjournal.com/users/james-gray" lang="" about="https://www.linuxjournal.com/users/james-gray" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">James Gray</a></div>
<div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>
More than 40% of software developers use the massively popular
software development tool Git as their primary source control tool. Those
new to the Git fold who are looking for a professional, up-to-date guide
to get them rolling have a new resource in Brent Laster's new book
<em>Professional Git</em>.
</p>
<p>
Laster's <a href="http://wrox.com">Wrox</a>-published title is more than just
a development manual: it gets users into the "Git mindset". The
book offers extensive discussion of corollaries to traditional systems
as well as considerations unique to Git to help one draw upon existing
skills while looking out—and planning for—the differences.
</p>
<img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1000009/12131f7.jpg" alt="" title="" class="imagecache-large-550px-centered" /><p>
Connected
labs and exercises are interspersed at key points to reinforce important
concepts and deepen understanding, while a focus on the practical goes
beyond technical tutorials to help users integrate the Git model into
real-world workflows. This book instructs users how to harness the power
and flexibility of Git to streamline the development cycle.
</p></div>
<div class="field field--name-node-link field--type-ds field--label-hidden field--item"> <a href="https://www.linuxjournal.com/content/brent-lasters-professional-git-wrox" hreflang="und">Go to Full Article</a>
</div>
</div>
</div>
Mon, 27 Feb 2017 14:51:52 +0000James Gray1339296 at https://www.linuxjournal.comNon-Linux FOSS: Git Yer Tortoise On!https://www.linuxjournal.com/content/non-linux-foss-git-yer-tortoise
<div data-history-node-id="1335701" class="layout layout--onecol">
<div class="layout__region layout__region--content">
<div class="field field--name-field-node-image field--type-image field--label-hidden field--item"> <img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/11664fossf1_0.jpg" width="550" height="421" alt="" typeof="foaf:Image" class="img-responsive" /></div>
<div class="field field--name-node-author field--type-ds field--label-hidden field--item">by <a title="View user profile." href="https://www.linuxjournal.com/users/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Shawn Powers</a></div>
<div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>
Git has become the most popular version-tracking platform around for
open-source projects. Whether you're using GitHub, Gitorious, Bitbucket or
similar,
or even if you're hosting the git repository yourself, accessing
the code is something us Linux users take for granted. For Windows users,
what seems commonplace to us (typing <code>git clone</code> on the command
line, for instance) is completely foreign to the regular point-and-click
world they're used to.
</p>
<img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1002061/11664fossf1.jpg" alt="" title="" class="imagecache-large-550px-centered" /><p>
Enter TortoiseGit. With a familiar GUI interface to the underlying git
system, TortoiseGit can make Windows-based open-source developers feel
right at home. It's open source itself, and it's part of the Tortoise
family, which includes TortoiseSVN for Subversion repositories and
TortoiseCVS for the Concurrent Versioning System. To check out the whole
family of Windows-based Tortoise clients, see the Wikipedia page at
<a href="http://en.wikipedia.org/wiki/TortoiseGit">http://en.wikipedia.org/wiki/TortoiseGit</a>.
</p></div>
<div class="field field--name-node-link field--type-ds field--label-hidden field--item"> <a href="https://www.linuxjournal.com/content/non-linux-foss-git-yer-tortoise" hreflang="und">Go to Full Article</a>
</div>
</div>
</div>
Thu, 15 May 2014 20:12:54 +0000Shawn Powers1335701 at https://www.linuxjournal.comGit - Revision Control Perfectedhttps://www.linuxjournal.com/content/git-revision-control-perfected
<div data-history-node-id="1023997" class="layout layout--onecol">
<div class="layout__region layout__region--content">
<div class="field field--name-field-node-image field--type-image field--label-hidden field--item"> <img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/10971f1.png" width="640" height="413" alt="" typeof="foaf:Image" class="img-responsive" /></div>
<div class="field field--name-node-author field--type-ds field--label-hidden field--item">by <a title="View user profile." href="https://www.linuxjournal.com/users/henry-van-styn" lang="" about="https://www.linuxjournal.com/users/henry-van-styn" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Henry Van Styn</a></div>
<div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>
In 2005, after just two weeks, Linus Torvalds completed the first version
of Git, an open-source version control system. Unlike typical centralized
systems, Git is based on a distributed model. It is extremely flexible and
guarantees data integrity while being powerful, fast and efficient. With
widespread and growing rates of adoption, and the increasing popularity
of services like GitHub, many consider Git to be the best version control
tool ever created.
</p>
<p>
Surprisingly, Linus had little interest in writing a version control tool
before this endeavor. He created Git out of necessity and frustration. The
Linux Kernel Project needed an open-source tool to manage
its massively distributed development effectively, and no existing tools were up to
the task.
</p>
<p>
Many aspects of Git's design are radical departures from the approach
of tools like CVS and Subversion, and they even differ significantly from
more modern tools like Mercurial. This is one of the reasons Git
is intimidating to many prospective users. But, if you throw away your
assumptions of how version control should work, you'll find that Git is
actually simpler than most systems, but capable of more.
</p>
<p>
In this article, I cover some of the fundamentals of how Git works and
stores data before moving on to discuss basic usage and work flow. I
found that knowing what is going on behind the scenes makes it much
easier to understand Git's many features and capabilities. Certain parts
of Git that I previously had found complicated suddenly were easy and
straightforward after spending a little time learning how it worked.
</p>
<p>
I find Git's design to be fascinating in and of itself. I peered behind
the curtain, expecting to find a massively complex machine, and instead saw
only a little hamster running in a wheel. Then I realized
a complicated design not only wasn't needed, but also wouldn't add
any value.
</p>
<h3>
Git Object Repository</h3>
<p>
Git, at its core, is a simple indexed name/value database. It stores
pieces of data (values) in "objects" with unique names. But, it does this
somewhat differently from most systems. Git operates on the principle of
"content-addressed storage", which means the names are derived from the
values. An object's name is chosen automatically by its content's SHA1
checksum—a 40-character string like this:
</p><pre><code>
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
</code></pre>
<p>
SHA1 is cryptographically strong, which guarantees a different checksum for
different data (the actual risk of two different pieces of data sharing
the same SHA1 checksum is infinitesimally small). The same chunk of data
always will have the same SHA1 checksum, which always will identify only
that chunk of data. Because object names are SHA1 checksums, they identify
the object's content while being truly globally unique—not just to one
repository, but to all repositories everywhere, forever.
</p></div>
<div class="field field--name-node-link field--type-ds field--label-hidden field--item"> <a href="https://www.linuxjournal.com/content/git-revision-control-perfected" hreflang="und">Go to Full Article</a>
</div>
</div>
</div>
Wed, 24 Aug 2011 14:00:00 +0000Henry Van Styn1023997 at https://www.linuxjournal.com