 |
| ||||
Intel only Git is an open source version control system designed to handle very large projects with speed and efficiency, but just as well suited for small personal repositories.
Git is especially popular in the open source community, serving as a development platform for projects like the Linux Kernel, WINE or X.org.
Git falls in the category of distributed source code management tools, similar to e.g. Mercurial or Bazaar. Every Git working directory is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. Still, Git stays extremely fast and space efficient.
Besides providing a version control system, Git also provides a generic low-level toolkit for directory content management and tree history storage. Traditionally, the toolkit is called the plumbing.
Aside the user interface coming with Git itself, several other projects (so-called porcelains) offer compatible version control interfaces.
Here are some key features of "Git":
· Distributed development. Like most other modern version control systems, Git gives each developer a local copy of the entire development history, and changes are copied from one such repository to another. These changes are imported as additional development branches, and can be merged in the same way as a locally developed branch. Repositories can be easily accessed via the efficient Git protocol (optionally wrapped in ssh for authentication and security) or simply using HTTP - you can publish your repository anywhere without any special webserver configuration required.
· Strong support for non-linear development. Git supports rapid and convenient branching and merging, and includes powerful tools for visualizing and navigating a non-linear development history.
· Efficient handling of large projects. Git is very fast and scales well even when working with large projects and long histories. It is commonly an order of magnitude faster than most other version control systems, and several orders of magnitude faster on some operations. It also uses an extremely efficient packed format for long-term revision storage that currently tops any other open source version control system.
· Cryptographic authentication of history. The Git history is stored in such a way that the name of a particular revision (a "commit" in Git terms) depends upon the complete development history leading up to that commit. Once it is published, it is not possible to change the old versions without it being noticed. Also, tags can be cryptographically signed.
· Toolkit design. Following the Unix tradition, Git is a collection of many small tools written in C, and a number of scripts that provide convenient wrappers. Git provides tools for both convenient human usage and easy scripting to perform new clever operations.
What's New in This Release: [ read full changelog ]
Fixes:
· The configuration parser had an unnecessary hardcoded limit on variable names that was not checked consistently.
· The "say" function in the test scaffolding incorrectly allowed "echo" to interpret "\a" as if it were a C-string asking for a BEL output.
· "git mergetool" feeds /dev/null as a common ancestor when dealing with an add/add conflict, but p4merge backend cannot handle it. Work it around by passing a temporary empty file.
· "git log -F -E --grep=''" failed to use the given pattern as extended regular expression, and instead looked for the string literally.
· "git grep -e pattern " asked the attribute system to read ":.gitattributes" file in the working tree, which was nonsense.
· A symbolic ref refs/heads/SYM was not correctly removed with "git branch -d SYM"; the command removed the ref pointed by SYM instead.
· Earlier we fixed documentation to hyphenate "remote-tracking branch" to clarify that these are not a remote entity, but unhyphenated spelling snuck in to a few pla...
Via: Git 1.8.0.1
No comments:
Post a Comment