Jon Loeliger - Version Control With Git
Here you can read online Jon Loeliger - Version Control With Git full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2009, publisher: OReilly Media, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Version Control With Git
- Author:
- Publisher:OReilly Media
- Genre:
- Year:2009
- Rating:4 / 5
- Favourites:Add to favourites
- Your mark:
Version Control With Git: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Version Control With Git" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Jon Loeliger: author's other books
Who wrote Version Control With Git? Find out the surname, the name of the author of the book and a list of all author's works by series.
Version Control With Git — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Version Control With Git" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Copyright 2009 Jon Loeliger
OReilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (.
Nutshell Handbook, the Nutshell Handbook logo, and the OReilly logo are registered trademarks of OReilly Media, Inc. Version Control with Git , the image of a long-eared bat, and related trade dress are trademarks of OReilly Media, Inc.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and OReilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps.
While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
While some familiarity with revision control systems will be good background material, a reader who is not familiar with any other system will still be able to learn enough about basic Git operations to be productive in a short while. More advanced readers should be able to gain insight into some of Gits internal design and thus master some of its more powerful techniques.
The main intended audience for this book should be familiar and comfortable with the Unix shell, basic shell commands, and general programming concepts.
Almost all examples and discussions in this book assume the reader has a Unix-like system with a command-line interface. The author developed these examples on Debian and Ubuntu Linux environments. The examples should work under other environments, such as Mac OS X or Solaris, but the reader can expect slight variations.
A few examples require root access on machines where system operations are needed. Naturally, in such situations you should have a clear understanding of the responsibilities of root access.
This book is organized as a progressive series of topics, each designed to build upon concepts introduced earlier. The first 10 chapters focus on concepts and operations that pertain to one repository. They form the foundation for more complex operations on multiple repositories covered in the final six chapters.
If you already have Git installed or have even used it briefly, you may not need the introductory and installation information in the first two chapters, nor even the quick tour presented in the third chapter.
The concepts covered in are essential for a firm grasp on Gits object model. They set the stage and prepare the reader for a clearer understanding of many of Gits more complex operations.
Chapters explains how Git derives and presents diffs.
Git provides a rich and powerful ability to join different branches of development. The basics of branch merging and resolving merge conflicts is covered in . A key insight into Gits model is the realization that all merging performed by Git happens in your local repository in the context of your current working directory.
The fundamentals of naming and exchanging data with another, remote repository are covered in .
to cover patch handling when direct exchange of repository information isnt possible using Gits native transfer protocols.
The remaining three chapters cover advanced topics: the use of hooks, combining projects and multiple repositories into a superproject, and interacting with Subversion repositories.
Git is still evolving rapidly because there is an active developer base. It is not that Git isnt mature enough to be used for development; rather, ongoing refinements and user interface issues are being enhanced regularly. Even as this book was being written, Git evolved. Apologies if I was unable to keep up accurately.
I do not give the command gitk the complete coverage that it deserves. If you like graphical representations of the history within a repository, you should explore gitk . Other history visualization tools exist as well, but they are not covered here either. Nor am I able to cover a rapidly evolving and growing host of other Git-related tools. Im not even able to cover all of Gits own core commands and options thoroughly in this book. Again, my apologies.
Perhaps, though, enough pointers, tips, and direction can be found here to inspire readers to do some of their own research and exploration!
The following typographical conventions are used in this book:
Indicates new terms, URLs, email addresses, filenames, and file extensions.
Constant widthUsed for program listings, as well as within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords.
Constant width boldShows commands or other text that should be typed literally by the user.
Constant width italicShows text that should be replaced with user-supplied values or by values determined by context.
This icon signifies a tip, suggestion, useful hint, or a general note.
This icon indicates a warning or caution.
Furthermore, you should be familiar with basic shell commands to manipulate files and directories. Many examples will contain commands such as these to add or remove directories, copy files, or create simple files:
$cp file.txt copy-of-file.txt$ mkdir newdirectory$ rm file$ rmdir somedir$ echo "Test line" > file$ echo "Another line" >> fileCommands that need to be executed with root permissions appear with a sudo operation :
# Install the Git core package$sudo apt-get install git-coreHow you edit files or effect changes within your working directory is pretty much up to you. You should be familiar with a text editor. In this book, Ill denote the process of editing a file by either a direct comment or a pseudocommand:
# edit file.c to have some new text$edit index.htmlThis book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless youre reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from OReilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your products documentation does require permission.
We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: Version Control with Git, by Jon Loeliger. Copyright 2009 Jon Loeliger, 978-0-596-52012-0.
If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at .
Font size:
Interval:
Bookmark:
Similar books «Version Control With Git»
Look at similar books to Version Control With Git. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book Version Control With Git and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.