Git版本控制管理(英文影印版)

.　　adding a file to your repository
　　configuring the commit author
　　making another commit
　　viewing your commits
　　viewing commit differences
　　removing and renaming files in your repository
　　making a copy of your repository
　configuration files.
　　configuring an alias
　inquiry
4.basic git concepts

　basic concepts
　　repositories
　　git object types
　　index
　　content-addressable names
　　git tracks content
　　pathname versus content
　object store pictures
　git concepts at work
　　inside the .git directory
　　objects, hashes, and blobs
　　files and trees
　　a note on git\'s use of sha1
　　tree hierarchies
　　commits
　　tags
5.file management and the index
　it\'s all about the index
　file classifications in git
　using git add
　some notes on using git commit
　　using git commit --all
　　writing commit log messages
　using git rm
　using git mv
　a note on tracking renames
　the .gitignore file
　a detailed view of git\'s object model and files
6.commits
　atomic changesets
　identifying commits
　　absolute commit names
　　refs and symrefs
　　relative commit names
　commit history
　　viewing old commits
　　commit graphs
　　commit ranges
　……
7.branches
8.diffs
9.merges
10.altering commits
11.remote repositories
12.repository management
13.patches
14.hooks
15.combining projects
16.using git with subversion repositories
lndex

.　　Indicates new terms, URLs, email addresses, filenames, and file extensions.
　　Constant width
　　Used 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 bold
　　Shows commands or other text that should be typed literally by the user.
　　Constant width italic
　　Shows 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 tiles 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" ）） file
　　Commands that need to be executed with root permissions appear with a sudo operation:
　　Install the Git core package
　　sudo apt-get install git-core
　　How 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, I'll 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.html
　　Using Code Examples
　　This 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 you're 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 O'Reilly 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 product's 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, byJon 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 permissions@oreilly.com.
　　Safari Books Online
　　SafariWhen you see a Safari~ Books Online icon on the cover of your favorite technology book, that means the book is available online through the O'Reilly Network Safari Bookshelf.
　　Safari offers a solution that's better than e-books. It's a virtual library that lets you easily search thousands of top tech books, cut and paste code samples, download chapters,and find quick answers when you need the most accurate, current information. Try it for free at http://my.safaribooksonline, com.
　　How to Contact Us
　　Please address comments and questions concerning this book to the publisher:
　　O'Reilly Media, Inc.
　　1005 Gravenstein Highway North
　　Sebastopol, CA 95472
　　800-998-9938 (in the United States or Canada)
　　707-829-0515 (international or local)
　　707-829-0104 (fax)
　　We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at:
　　http ://www. or eilly.com/ catalog/9 7 80 5 9 6 5 2 012 0 /
　　To comment or ask technical questions about this book, send email to:
　　bookquestions@oreilly, com
　　For more information about our books, conferences, Resource Centers, and the O'Reilly Network, see our website at:
　　http://www, oreilly, com
　　Acknowledgments
　　This work would not have been possible without the help of many other people. I'd like to thank Avery Pennarun for contributing substantial material to Chapters 14,15, and 16. He also contributed some material to Chapters 4 and 9. His help was appreciated. I'd like to publicly thank those who took time to review the book at various stages: Robert P. J. Day, Alan Hasty, Paul Jimenez, Barton Massey, Tom Rix, Jamey Sharp, Sarah Sharp, Larry Streepy, Andy Wilcox, and Andy Wingo.
　　Also, I'd like to thank my wife, Rhonda, and daughters, Brandi and Heather, who provided moral support, gentle nudging, Pinot Noir, and the occasional grammar tip.And thanks to Mylo, my long-haired dachshund, who spent the entire writing process curled up lovingly in my lap. I'd like to add a special thanks to K.C. Dignan, who supplied enough moral support and double-stick butt tape to keep my behind in my chair long enough to finish this book!
　　Finally, I would like to thank the staff at O'Reilly as well as my editors, Andy Oram and Martin Streicher.