progit compiling

Author: amejiarosario

book-pro/A-git-in-other-environments.asc

@@ -0,0 +1,28 @@
+[[A-git-in-other-environments]]
+[appendix]
+== Git in Other Environments
+
+If you read through the whole book, you've learned a lot about how to use Git at the command line.
+You can work with local files, connect your repository to others over a network, and work effectively with others.
+But the story doesn't end there; Git is usually used as part of a larger ecosystem, and the terminal isn't always the best way to work with it.
+Now we'll take a look at some of the other kinds of environments where Git can be useful, and how other applications (including yours) work alongside Git.
+
+include::book/A-git-in-other-environments/sections/guis.asc[]
+
+include::book/A-git-in-other-environments/sections/visualstudio.asc[]
+
+include::book/A-git-in-other-environments/sections/visualstudiocode.asc[]
+
+include::book/A-git-in-other-environments/sections/eclipse.asc[]
+
+include::book/A-git-in-other-environments/sections/sublimetext.asc[]
+
+include::book/A-git-in-other-environments/sections/bash.asc[]
+
+include::book/A-git-in-other-environments/sections/zsh.asc[]
+
+include::book/A-git-in-other-environments/sections/powershell.asc[]
+
+=== Summary
+
+You've learned how to harness Git's power from inside the tools that you use during your everyday work, and also how to access Git repositories from your own programs.

book-pro/B-embedding-git-in-your-applications.asc

@@ -0,0 +1,20 @@
+[[B-embedding-git-in-your-applications]]
+[appendix]
+== Embedding Git in your Applications
+
+If your application is for developers, chances are good that it could benefit from integration with source control.
+Even non-developer applications, such as document editors, could potentially benefit from version-control features, and Git's model works very well for many different scenarios.
+
+If you need to integrate Git with your application, you have essentially two options: spawn a shell and call the `git` command-line program, or embed a Git library into your application.
+Here we'll cover command-line integration and several of the most popular embeddable Git libraries.
+
+include::book/B-embedding-git/sections/command-line.asc[]
+
+include::book/B-embedding-git/sections/libgit2.asc[]
+
+include::book/B-embedding-git/sections/jgit.asc[]
+
+include::book/B-embedding-git/sections/go-git.asc[]
+
+include::book/B-embedding-git/sections/dulwich.asc[]
+

book-pro/C-git-commands.asc

@@ -0,0 +1,2 @@
+This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
+To view a copy of this license, visit https://creativecommons.org/licenses/by-nc-sa/3.0 or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.

book-pro/LICENSE.asc

@@ -0,0 +1,42 @@
+= Pro Git, Second Edition
+
+Welcome to the second edition of the Pro Git book.
+
+You can find this book online at: https://git-scm.com/book
+
+Like the first edition, the second edition of Pro Git is open source under a Creative Commons license.
+
+A couple of things have changed since open sourcing the first edition.
+For one, we've moved from Markdown to the amazing Asciidoc format for the text of the book.
+
+We've also moved to keeping the translations in separate repositories rather than subdirectories of the English repository.
+See link:TRANSLATING.md[the translating document] for more information.
+
+== How To Generate the Book
+
+You can generate the e-book files manually with Asciidoctor.
+If you run the following you _may_ actually get HTML, Epub, Mobi and PDF output files:
+
+----
+$ bundle install
+$ bundle exec rake book:build
+Converting to HTML...
+ -- HTML output at progit.html
+Converting to EPub...
+ -- Epub output at progit.epub
+Converting to Mobi (kf8)...
+ -- Mobi output at progit.mobi
+Converting to PDF...
+ -- PDF output at progit.pdf
+----
+
+== Signaling an Issue
+
+Before signaling an issue, please check that there isn't already a similar one in the bug tracking system.
+
+Also, if this issue has been spotted on the git-scm.com site, please cross-check that it is still present in this repo.
+The issue may have already been corrected, but the changes have not been deployed yet.
+
+== Contributing
+
+If you'd like to help out by making a change, take a look at the link:CONTRIBUTING.md[contributor's guide].

book-pro/Pro.ico

@@ -0,0 +1,51 @@
+namespace :book do
+  desc 'build basic book formats'
+  task :build do
+
+    begin
+      version_string = ENV['TRAVIS_TAG'] || `git describe --tags`.chomp
+      if version_string.empty?
+        version_string = '0'
+      end
+      date_string = Time.now.strftime("%Y-%m-%d")
+
+      # puts "Generating contributors list"
+      # `git shortlog -s | grep -v -E "(Straub|Chacon)" | cut -f 2- | column -c 120 > book/contributors.txt`
+
+      params = "-D dist -a revnumber='#{version_string}' -a revdate='#{date_string}'"
+
+      # require = '--trace --require=asciidoctor-diagram'
+      # require = '--trace -r asciidoctor-diagram'
+      require = ''
+
+      require_pdf = '-r ./config/extensions/asciidoctor-pdf-extensions.rb'
+      require_pdf = ''
+
+      puts "\r\n>> Converting to HTML..."
+      cmd = "asciidoctor #{require} #{params} progit.asc 2>&1"
+      puts cmd
+      puts `#{cmd}`
+      puts "\t-- HTML output at progit.html"
+
+      puts "\r\nConverting to PDF... (this one takes a while)"
+      cmd = "bundle exec asciidoctor-pdf #{require} #{require_pdf} #{params} progit.asc 2>&1"
+      puts cmd
+      puts `#{cmd}`
+      puts " -- PDF output at progit.pdf"
+
+      puts "\r\n>> Converting to EPub..."
+      # cmd = "bundle exec asciidoctor-epub3 #{require} -a ebook-validate #{params} progit.asc 2>&1"
+      cmd = "bundle exec asciidoctor-epub3 #{require} #{params} progit.asc 2>&1"
+      puts cmd
+      puts `#{cmd}`
+      puts "\t-- Epub output at progit.epub"
+
+      puts "\r\nConverting to Mobi (kf8)..."
+      puts `bundle exec asciidoctor-epub3 #{params} -a ebook-format=kf8 progit.asc 2>&1`
+      puts " -- Mobi output at progit.mobi"
+
+    end
+  end
+end
+
+task :default => "book:build"

book-pro/README.asc

@@ -0,0 +1,11 @@
+== Translation Notes
+
+After forking this repository to translate the work, this file is where the notes for coordinating the translation work would go.
+Things like standardizing on words and expressions so that the work is consistent or notes on how the contributing process is to be handled.
+
+As a translation maintainer, also feel free to modify or completely rewrite the README file to contain instructions specific to your translation.
+
+=== Translation Status
+
+As the work is translated, please update the `status.json` file to indicate the rough percentage complete each file is.
+This will be shown on various pages to let people know how much work is left to be done.

book-pro/Rakefile

@@ -0,0 +1,61 @@
+=== About Version Control
+
+(((version control)))
+What is ``version control'', and why should you care?
+Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.
+For the examples in this book, you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer.
+
+If you are a graphic or web designer and want to keep every version of an image or layout (which you would most certainly want to), a Version Control System (VCS) is a very wise thing to use.
+It allows you to revert selected files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more.
+Using a VCS also generally means that if you screw things up or lose files, you can easily recover.
+In addition, you get all this for very little overhead.
+
+==== Local Version Control Systems
+
+(((version control,local)))
+Many people's version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they're clever).
+This approach is very common because it is so simple, but it is also incredibly error prone.
+It is easy to forget which directory you're in and accidentally write to the wrong file or copy over files you don't mean to.
+
+To deal with this issue, programmers long ago developed local VCSs that had a simple database that kept all the changes to files under revision control.
+
+.Local version control.
+image::images/local.png[Local version control diagram]
+
+One of the most popular VCS tools was a system called RCS, which is still distributed with many computers today.
+RCS works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all the patches.
+
+==== Centralized Version Control Systems
+
+(((version control,centralized)))
+The next major issue that people encounter is that they need to collaborate with developers on other systems.
+To deal with this problem, Centralized Version Control Systems (CVCSs) were developed.
+These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients that check out files from that central place. (((CVS)))(((Subversion)))(((Perforce)))
+For many years, this has been the standard for version control.
+
+.Centralized version control.
+image::images/centralized.png[Centralized version control diagram]
+
+This setup offers many advantages, especially over local VCSs.
+For example, everyone knows to a certain degree what everyone else on the project is doing.
+Administrators have fine-grained control over who can do what, and it's far easier to administer a CVCS than it is to deal with local databases on every client.
+
+However, this setup also has some serious downsides.
+The most obvious is the single point of failure that the centralized server represents.
+If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they're working on.
+If the hard disk the central database is on becomes corrupted, and proper backups haven't been kept, you lose absolutely everything -- the entire history of the project except whatever single snapshots people happen to have on their local machines.
+Local VCS systems suffer from this same problem -- whenever you have the entire history of the project in a single place, you risk losing everything.
+
+==== Distributed Version Control Systems
+
+(((version control,distributed)))
+This is where Distributed Version Control Systems (DVCSs) step in.
+In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don't just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history.
+Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it.
+Every clone is really a full backup of all the data.
+
+.Distributed version control.
+image::images/distributed.png[Distributed version control diagram]
+
+Furthermore, many of these systems deal pretty well with having several remote repositories they can work with, so you can collaborate with different groups of people in different ways simultaneously within the same project.
+This allows you to set up several types of workflows that aren't possible in centralized systems, such as hierarchical models.

book-pro/TRANSLATION_NOTES.asc

@@ -0,0 +1,11 @@
+=== The Command Line
+
+There are a lot of different ways to use Git.
+There are the original command-line tools, and there are many graphical user interfaces of varying capabilities.
+For this book, we will be using Git on the command line.
+For one, the command line is the only place you can run _all_ Git commands -- most of the GUIs implement only a partial subset of Git functionality for simplicity.
+If you know how to run the command-line version, you can probably also figure out how to run the GUI version, while the opposite is not necessarily true.
+Also, while your choice of graphical client is a matter of personal taste, _all_ users will have the command-line tools installed and available.
+
+So we will expect you to know how to open Terminal in macOS or Command Prompt or PowerShell in Windows.
+If you don't know what we're talking about here, you may need to stop and research that quickly so that you can follow the rest of the examples and descriptions in this book.