FACTOID # 143: If someone you know died from falling out of a tree, you’re probably Brazilian.
 
 Home   Encyclopedia   Statistics   Countries A-Z   Flags   Maps   Education   Forum   FAQ   About 
 
 
 
WHAT'S NEW
RECENT ARTICLES
More Recent Articles »
 

SEARCH ALL

FACTS & STATISTICS    Advanced view

Search encyclopedia, statistics and forums:

 

 

(* = Graphable)

 

 


Encyclopedia > Git (software)
Git
Git logo
Design by Linus Torvalds
Developed by Junio Hamano, Linus Torvalds
Latest release 1.5.5.3[1] / May 26, 2008
Written in C, Bourne Shell, Perl[2]
OS POSIX
Genre Revision control system
License GNU General Public License v2
Website http://git.or.cz/

Git is a distributed revision control / software code management project created by Linus Torvalds, initially for the Linux kernel development. Image File history File links This is a lossless scalable vector image. ... Software design is the process that starts from a problem for which there is currently no acceptable (software) solution, and ends when such a solution has been created. ... Linus Benedict Torvalds ( ; ; born December 28, 1969 in Helsinki, Finland) is a Finnish software engineer best known for initiating the development of the Linux kernel. ... For other uses, see Software developer (disambiguation). ... Linus Benedict Torvalds ( ; ; born December 28, 1969 in Helsinki, Finland) is a Finnish software engineer best known for initiating the development of the Linux kernel. ... Code complete redirects here. ... is the 146th day of the year (147th in leap years) in the Gregorian calendar. ... 2008 (MMVIII) is the current year, a leap year that started on Tuesday of the Anno Domini (or common era), in accordance with the Gregorian calendar. ... A programming language is an artificial language that can be used to control the behavior of a machine, particularly a computer. ... C is a general-purpose, block structured, procedural, imperative computer programming language developed in 1972 by Dennis Ritchie at the Bell Telephone Laboratories for use with the Unix operating system. ... The Bourne shell, or sh, was the default Unix shell of Unix Version 7, and replaced the Thompson shell, whose executable file had the same name, sh. ... For other uses, see Perl (disambiguation). ... An operating system (OS) is a software that manages computer resources and provides programmers with an interface used to access those resources. ... POSIX or Portable Operating System Interface[1] is the collective name of a family of related standards specified by the IEEE to define the application programming interface (API) for software compatible with variants of the Unix operating system. ... The Revision Control System (RCS) is a software implementation of revision control that automates the storing, retrieval, logging, identification, and merging of revisions. ... A software license is a legal agreement which may take the form of a proprietary or gratuitous license as well as a memorandum of contract between a producer and a user of computer software. ... GPL redirects here. ... A website (alternatively, web site or Web site) is a collection of Web pages, images, videos or other digital assets that is hosted on one or more web servers, usually accessible via the Internet. ... Revision control (also known as version control (system) (VCS), source control or (source) code management (SCM)) is the management of multiple revisions of the same unit of information. ... Linus Benedict Torvalds ( ; ; born December 28, 1969 in Helsinki, Finland) is a Finnish software engineer best known for initiating the development of the Linux kernel. ... The Linux kernel is a Unix-like operating system kernel. ...


Git's design was inspired by BitKeeper and Monotone.[3][4] Git was originally designed only as a low-level engine that others could use to write front ends such as Cogito or StGIT.[5] However, the core Git project has since become a complete revision control system that is usable directly.[6] Several high-profile software projects now use Git for revision control,[7] most notably the Linux kernel, X.org Server, One Laptop per Child (OLPC) core development,[8] and the Ruby on Rails web framework. [9] BitKeeper is a software tool for revision control (configuration management, SCM, etc. ... Monotone is an open source software tool for revision control. ... Cogito (originally git-pasky) is a revision control system layered on top of Git. ... The Linux kernel is a Unix-like operating system kernel. ... The X.Org Server (officially the ) is the official reference implementation of the X Window System. ... OLPC redirects here. ... Ruby on Rails is a free web application framework designed to make web development faster, simpler and more efficient. ...


Git's current software maintenance is overseen by Junio Hamano. Released under the GNU General Public License, version 2, Git is free software. In software engineering, software maintenance is the process of enhancing and optimizing deployed software (software release), as well as remedying defects. ... GPL redirects here. ... Free software is software that can be used, studied, and modified without restriction, and which can be copied and redistributed in modified or unmodified form either without restriction, or with minimal restrictions only to ensure that further recipients can also do these things. ...

Contents

Name

Linus Torvalds has quipped about the name "git", which is British English slang for a stupid or unpleasant person: [10] Linus Benedict Torvalds ( ; ; born December 28, 1969 in Helsinki, Finland) is a Finnish software engineer best known for initiating the development of the Linux kernel. ... Wit is a form of intellectual humour, based on manipulation of concepts; a wit is someone who excels in witty remarks, typically in conversation and spontaneously, since wit carries the connotation of speed of thought. ... British English (BrE, BE, en-GB) is the broad term used to distinguish the forms of the English language used in the United Kingdom from forms used elsewhere in the Anglophone world. ...

“ I'm an egotistical bastard, and I name all my projects after myself. First Linux, now git. ”

The official Git wiki also gives a number of alternative explanations for the name.[11] This article is about operating systems that use the Linux kernel. ...


Characteristics

Git's design is a synthesis of Torvalds's experience maintaining a large distributed development project, his intimate knowledge of file system performance, and an urgent need to produce a working system in short order. (See the history section for details.) These influences led to the following implementation choices:

  • Strong support for non-linear development. Git supports rapid branching and merging, and includes specific tools for visualizing and navigating a non-linear development history. A core assumption in Git is that a change will be merged more often than it is written, as it is passed around various reviewers.
  • Distributed development. Like Darcs, BitKeeper, Mercurial, SVK, Bazaar and Monotone, 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 published via HTTP, FTP, ssh, rsync, or a Git protocol. Git also has a CVS server emulation, which enables the use of existing CVS clients and IDE plugins to access Git repositories.
  • Subversion and svk repositories can be used directly with git-svn.
  • Efficient handling of large projects. Torvalds has described Git as being very fast and scalable,[12] and performance tests done by Mozilla showed it was an order of magnitude faster than other revision control systems, and two orders of magnitude faster on some operations.[13][14]
  • 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. (Mercurial and Monotone also has this property.)
  • Toolkit design. Git was designed as a set of programs written in C, and a number of shell scripts that provide wrappers around those programs.[15] Although most of those scripts have been rewritten in C as part of an ongoing effort to port it to Microsoft Windows, the design remains, and it is easy to chain the components together to do other clever things.[16]
  • Pluggable merge strategies. As part of its toolkit design, Git has a well-defined model of an incomplete merge, and it has multiple algorithms for completing it, culminating in telling the user that it is unable to complete the merge automatically and manual editing is required.
  • Garbage accumulates unless collected. Aborting operations or backing out changes will leave useless dangling objects in the database. These are generally a small fraction of the continuously growing history of wanted objects, but reclaiming the space using git-gc --prune can be slow.[17]

One property of Git is that it snapshots directory trees of files. The earliest systems for tracking versions of source code, SCCS and RCS, worked on individual files and emphasized the space savings to be gained from delta encoding the (mostly similar) versions. Later revision control systems maintained this notion of a file having an identity across multiple revisions of a project. Darcs is a distributed revision control system by David Roundy designed to replace the centralized CVS. Several noticeable differences in the design aim for simple use and powerful features. ... BitKeeper is a software tool for revision control (configuration management, SCM, etc. ... Mercurial is a cross-platform, distributed source management tool for software developers. ... SVK is a decentralized version control system written in Perl, with a design comparable to BitKeeper and GNU arch. ... Bazaar is a revision control system which implements the GNU arch protocol. ... Monotone is an open source software tool for revision control. ... Hypertext Transfer Protocol (HTTP) is a communications protocol used to transfer or convey information on intranets and the World Wide Web. ... This article is about the File Transfer Protocol standardised by the IETF. For other file transfer protocols, see File transfer protocol (disambiguation). ... SSH redirects here. ... In computing, rsync is a computer program for Unix systems which synchronizes files and directories from one location to another while minimizing data transfer using delta encoding when appropriate. ... Mozilla was the official, public, original name of Mozilla Application Suite by the Mozilla Foundation, nowadays called SeaMonkey suite. ... An order of magnitude is the class of scale or magnitude of any amount, where each class contains values of a fixed ratio to the class preceding it. ... Mercurial is a cross-platform, distributed source management tool for software developers. ... Monotone is an open source software tool for revision control. ... C is a general-purpose, block structured, procedural, imperative computer programming language developed in 1972 by Dennis Ritchie at the Bell Telephone Laboratories for use with the Unix operating system. ... Garbage, in the context of computer science, refers to objects, data, or other regions of the memory of a computer system (or other system resources), which will not be used in any future computation by the system, or by a program running on it. ... In computer science, garbage collection (GC) is a form of automatic memory management. ... Source Code Control System (SCCS) was the first source code revision control system. ... The Revision Control System (RCS) is a software implementation of revision control that automates the storing, retrieval, logging, identification, and merging of revisions. ... Delta encoding is a way of storing or transmitting data in form of differences between sequential data rather than complete files. ...


Torvalds rejected this concept;[18] consequently, Git does not explicitly record file revision relationships at any level below the source code tree. This has some significant consequences:

  • It is slightly more expensive to examine the change history of a single file than the whole project.[19] To obtain a history of changes affecting a given file, Git must walk the global history and then determine whether each change modified that file. This method of examining history does, however, let Git produce with equal efficiency a single history showing the changes to an arbitrary set of files. For example, a subdirectory of the source tree plus an associated global header file is a very common case.
  • Renames are handled implicitly rather than explicitly. A common complaint with CVS is that it uses the name of a file to identify its revision history, so moving or renaming a file is not possible without either interrupting its history, or renaming the history and thereby making the history inaccurate. Most post-CVS revision control systems solve this by giving a file a unique long-lived name (a sort of inode number) that survives renaming. Git does not record such an identifier, and this is claimed as an advantage.[20][21] Source code files are sometimes split or merged as well as simply renamed,[22] and recording this as a simple rename would freeze an inaccurate description of what happened in the (immutable) history. Git addresses the issue by detecting renames while browsing the history of snapshots rather than recording it when making the snapshot.[23] (Briefly, given a file in revision N, a file of the same name in revision N−1 is its default ancestor. However, when there is no like-named file in revision N−1, Git searches for a file that existed only in revision N−1 and is very similar to the new file.) However, it does require more CPU-intensive work every time history is reviewed, and a number of options to adjust the heuristics.

Additionally, people are sometimes upset by the storage model: The Concurrent Versions System (CVS), also known as the Concurrent Versioning System, is an open-source version control system invented and developed by Dick Grune in the 1980s. ... In computing, an inode is a data structure on a traditional Unix-style file system such as UFS. An inode stores basic information about a regular file, directory, or other file system object. ... Source code (commonly just source or code) is any series of statements written in some human-readable computer programming language. ... CPU redirects here. ...

  • Periodic explicit object packing. Git stores each newly created object as a separate file. Although individually compressed, this takes a great deal of space and is inefficient. This is solved by the use of "packs" that store a large number of objects in a single file (or network byte stream), delta-compressed among themselves. Packs are compressed using the heuristic that files with the same name are probably similar, but do not depend on it for correctness. Newly created objects (newly added history) are still stored singly, and periodic repacking is required to maintain space efficiency. Git does periodic repacking automatically but manual repacking is also possible with the git-gc command.

Git implements several merging strategies; a non-default can be selected at merge time:[24] In computer science, besides the common use as rule of thumb (see heuristic), the term heuristic has two well-defined technical meanings. ...

resolve
the traditional 3-way merge algorithm.
recursive
This is the default when pulling or merging one branch, and is a variant of the 3-way merge algorithm. "When there are more than one common ancestors that can be used for 3-way merge, it creates a merged tree of the common ancestors and uses that as the reference tree for the 3-way merge. This has been reported to result in fewer merge conflicts without causing mis-merges by tests done on actual merge commits taken from Linux 2.6 kernel development history. Additionally this can detect and handle merges involving renames."[25]
octopus
This is the default when merging more than two heads.

Merging is the act of reconciling multiple changes made to different copies of the same file. ...

Early history

Git development began after many Linux kernel developers were forced to give up access to the proprietary BitKeeper system (see BitKeeper - Pricing change). The ability to use BitKeeper free of charge had been withdrawn by the copyright holder Larry McVoy after he claimed Andrew Tridgell had reverse engineered the BitKeeper protocols in violation of the BitKeeper license. At Linux.Conf.Au 2005, Tridgell demonstrated during his keynote that the reverse engineering process he had used was simply to telnet to the appropriate port of a Bitkeeper server and type "help".[26] The Linux kernel is a Unix-like operating system kernel. ... Proprietary software is software with restrictions on copying and modifying as enforced by the proprietor. ... BitKeeper is a software tool for revision control (configuration management, SCM, etc. ... Larry McVoy (b. ... Tridge redirects here. ... Reverse engineering (RE) is the process of taking something (a device, an electrical component, a software program, etc. ... linux. ... For the packet switched network, see Telenet. ...


Torvalds wanted a distributed system that he could use like BitKeeper, but none of the available free systems met his needs, particularly his performance needs. From an e-mail he wrote on April 7, 2005 while writing the first prototype:[27] April 7 is the 97th day of the year in the Gregorian calendar (98th in leap years). ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ...

“

However, the SCMs I've looked at make this hard. One of the things (the main thing, in fact) I've been working at is to make that process really efficient. If it takes half a minute to apply a patch and remember the changeset boundary etc. (and quite frankly, that's fast for most SCMs around for a project the size of Linux), then a series of 250 emails (which is not unheard of at all when I sync with Andrew, for example) takes two hours. If one of the patches in the middle doesn't apply, things are bad bad bad. Revision control (also known as version control (system) (VCS), source control or (source) code management (SCM)) is the management of multiple revisions of the same unit of information. ...


Now, BK wasn't a speed demon either (actually, compared to everything else, BK is a speed deamon [sic], often by one or two orders of magnitude), and took about 10–15 seconds per email when I merged with Andrew. HOWEVER, with BK that wasn't as big of an issue, since the BK<->BK merges were so easy, so I never had the slow email merges with any of the other main developers. So a patch-application-based SCM “merger” actually would need to be faster than BK is. Which is really really really hard.


So I'm writing some scripts to try to track things a whole lot faster. Initial indications are that I should be able to do it almost as quickly as I can just apply the patch, but quite frankly, I'm at most half done, and if I hit a snag maybe that's not true at all. Anyway, the reason I can do it quickly is that my scripts will not be an SCM, they'll be a very specific “log Linus' state” kind of thing. That will make the linear patch merge a lot more time-efficient, and thus possible.


(If a patch apply takes three seconds, even a big series of patches is not a problem: if I get notified within a minute or two that it failed half-way, that's fine, I can then just fix it up manually. That's why latency is critical—if I'd have to do things effectively “offline”, I'd by definition not be able to fix it up when problems happen).

 ”

Torvalds had several design criteria:

  1. Take CVS as an example of what not to do; if in doubt, make the exact opposite decision. To quote Torvalds, speaking somewhat tongue-in-cheek:
    “For the first 10 years of kernel maintenance, we literally used tarballs and patches, which is a much superior source control management system than CVS is, but I did end up using CVS for 7 years at a commercial company [presumably Transmeta] and I hate it with a passion. When I say I hate CVS with a passion, I have to also say that if there are any SVN (Subversion) users in the audience, you might want to leave. Because my hatred of CVS has meant that I see Subversion as being the most pointless project ever started. The slogan of Subversion for a while was ‘CVS done right’, or something like that, and if you start with that kind of slogan, there's nowhere you can go. There is no way to do CVS right.”[28]
  2. Support a distributed, BitKeeper-like workflow
    “BitKeeper was not only the first source control system that I ever felt was worth using at all, it was also the source control system that taught me why there's a point to them, and how you actually can do things. So Git in many ways, even though from a technical angle it is very very different from BitKeeper (which was another design goal, because I wanted to make it clear that it wasn't a BitKeeper clone), a lot of the flows we use with Git come directly from the flows we learned from BitKeeper.”[28]
  3. Very strong safeguards against corruption, either accidental or malicious[29][28]
  4. Very high performance

The first three criteria eliminated every pre-existing version control system except for Monotone, and the fourth excluded everything.[28] So, immediately after the 2.6.12-rc2 Linux kernel development release,[28] he set out to write his own.[28] The Concurrent Versions System (CVS), also known as the Concurrent Versioning System, is an open-source version control system invented and developed by Dick Grune in the 1980s. ... Transmeta NASDAQ: TMTA develops computing technologies with a focus on reducing power consumption in electronic devices. ... In computing, Subversion (SVN) is a version control system (VCS) initiated in 2000 by CollabNet Inc. ... Monotone is an open source software tool for revision control. ...


The development of Git began on April 3, 2005.[30] The project was announced on April 6,[31] and became self-hosting as of April 7.[32] The first merge of multiple branches was done on April 18.[33] Torvalds achieved his performance goals; on April 29, the nascent Git was benchmarked recording patches to the Linux kernel tree at the rate of 6.7 per second.[34] On June 16, the kernel 2.6.12 release was managed by Git.[35] is the 93rd day of the year (94th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 96th day of the year (97th in leap years) in the Gregorian calendar. ... Self-hosting refers to the use of a computer program as part of the toolchain or operating system that produces new versions of that same program—for example, a compiler that can compile its own source code. ... April 7 is the 97th day of the year in the Gregorian calendar (98th in leap years). ... is the 108th day of the year (109th in leap years) in the Gregorian calendar. ... is the 119th day of the year (120th in leap years) in the Gregorian calendar. ... is the 167th day of the year (168th in leap years) in the Gregorian calendar. ...


While strongly influenced by BitKeeper, Torvalds deliberately attempted to avoid conventional approaches, leading to a very novel design.[36] He developed the system until it was usable by technical users, then turned over maintenance on July 26, 2005 to Junio Hamano, a major contributor to the project.[37] Hamano was responsible for the 1.0 release on December 21, 2005,[38] and remains the maintainer as of April 2008. is the 207th day of the year (208th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 355th day of the year (356th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ...


Implementation

Like BitKeeper, Git does not use a centralized server. However, Git's primitives are not inherently a SCM system. Torvalds explains,[39] Software Configuration Management (SCM) is part of configuration management (CM). ...

“

In many ways you can just see git as a filesystem — it's content-addressable, and it has a notion of versioning, but I really really designed it coming at the problem from the viewpoint of a filesystem person (hey, kernels is what I do), and I actually have absolutely zero interest in creating a traditional SCM system.

 ”
(Note that his opinion has changed since then.)[40]

Git has two data structures, a mutable index that caches information about the working directory and the next revision to be committed, and an immutable, append-only object database containing four types of objects: A binary tree, a simple type of branching linked data structure. ...

  • A blob object is the content of a file. Blob objects have no names, timestamps, or other metadata.
  • A tree object is the equivalent of a directory: it contains a list of filenames, each with some type bits and the name of a blob or tree object that is that file, symbolic link, or directory's contents. This object describes a snapshot of the source tree.
  • A commit object links tree objects together into a history. It contains the name of a tree object (of the top-level source directory), a timestamp, a log message, and the names of zero or more parent commit objects.
  • A tag object is a container that contains reference to another object and can hold additional meta-data related to another object. Most commonly it is used to store a digital signature of a commit object corresponding to a particular release of the data being tracked by Git.

The object database can hold any kind of object. An intermediate layer, the index, serves as connection point between the object database and the working tree. This article is about computer files and file systems in general terms. ...


Each object is identified by a SHA-1 hash of its contents. Git computes the hash, and uses this value for the object's name. The object is put into a directory matching the first two characters of its hash. The rest of the hash is used as the file name for that object. SHA redirects here. ... In cryptography, a cryptographic hash function is a hash function with certain additional security properties to make it suitable for use as a primitive in various information security applications, such as authentication and message integrity. ...


Git stores each revision of a file as a unique blob object. The relationships between the blobs can be found through examining the tree and commit objects. Newly added objects are stored in their entirety using zlib compression. This can consume a large amount of hard disk space quickly, so objects can be combined into packs, which use delta compression to save space, storing blobs as their changes relative to other blobs. zlib is an open-source, cross-platform data compression library. ... Typical hard drives of the mid-1990s. ... In software configuration management (SCM), a delta is a type of file in which the difference (or diff) between two successive versions, is recorded. ...


Portability

Git is targeted to run on Linux, but can be used on other Unix-like operating systems including BSD, Solaris and Darwin. Git is extremely fast on POSIX-based systems such as Linux.[41] This article is about operating systems that use the Linux kernel. ... Diagram of the relationships between several Unix-like systems A Unix-like operating system is one that behaves in a manner similar to a Unix system, while not necessarily conforming to or being certified to any version of the Single UNIX Specification. ... BSD redirects here. ... The Solaris Operating System, usually known simply as Solaris, is a free Unix-based operating system introduced by Sun Microsystems in 1992 as the successor to SunOS. Solaris is known for its scalability, especially on SPARC systems, as well for being the origin for many innovative features such as DTrace... Darwin is a free and open source, Unix-like operating system first released by Apple Inc. ... POSIX or Portable Operating System Interface[1] is the collective name of a family of related standards specified by the IEEE to define the application programming interface (API) for software compatible with variants of the Unix operating system. ...


Git also runs on Windows. There are actually two options, the "official" one requiring the installation and use of Cygwin (a POSIX emulation).[42] Git is noticeably slower on Windows especially for commands written in shell scripts[43] primarily due to heavy cost of fork emulation performed by Cygwin. However, the recent rewriting of many shell commands in C have resulted in significant speed improvement on Windows.[44] Regardless, many people find Cygwin installation too large and invasive for typical Windows use.[45] Windows redirects here. ... Cygwin (pronounced ) is a collection of free software tools originally developed by Cygnus Solutions to allow various versions of Microsoft Windows to act similar to a Unix system. ... A fork, when applied to computing occurs when a process creates a copy of itself, which then acts as a child of the original process, now called the parent. More generally, a fork in a multithreading environment means that a thread of execution is duplicated. ... C is a general-purpose, block structured, procedural, imperative computer programming language developed in 1972 by Dennis Ritchie at the Bell Telephone Laboratories for use with the Unix operating system. ...


A native Microsoft Windows port (using MinGW) is approaching completion,[46] with versions of installers ready for testing (under the names "Git" and "msysgit", where "Git" is aimed for users)[47]. While still slower than the Linux version,[48], it is acceptably fast[49] and is reported to be usable in production, with only minor awkwardness.[50] In particular, some commands are not available from the GUIs, and must be invoked from the command line. Many issues have been resolved, such as handling of CRLF line endings and Windows' lack of POSIX compatibility.[51] MinGW (Minimalist GNU for Windows), formerly mingw32, is a native software port of the GNU Compiler Collection (GCC) to Microsoft Windows along with a set of freely distributable import libraries and header files for the Windows API. MinGW allows developers to create native Microsoft Windows applications. ... CRLF is a sequence of control characters consisting of a carriage return (CR) and a line feed (LF). ...


Many projects support both POSIX and Windows. Such projects typically avoid using an SCM system that poorly supports Windows, even if most developers use POSIX-based systems. Examples of projects that have publicly ruled out any use of Git, due to Git's poor support of Windows, include Mozilla[52] and Ruby.[53] Mozilla was the official, public, original name of Mozilla Application Suite by the Mozilla Foundation, nowadays called SeaMonkey suite. ... Ruby is a reflective, dynamic, object-oriented programming language. ...


In some cases (particularly for anonymous remote access), support for Windows users can be provided via git-cvsserver (which emulates a CVS server, allowing use of Windows CVS clients). Other alternatives include:[54]

  • Eclipse IDE-based Git client, based on a pure Java implementation of Git's internals: egit
  • NetBeans IDE support for Git is under development.
  • A Windows Explorer extension (a project for a TortoiseCVS/TortoiseSVN-lookalike was started already) Git Cheetah
  • Git on MSYS is already used in production environments. It comes in an installer package, supports Git command-line usage (both Git-Bash and Windows Command-line) and Git-GUI/Gitk and also has basic Explorer integration [1]

"Libifying" the lowest-level Git operations would in theory enable re-implementation of the lowest-level components for Windows without rewriting the rest.[55] Eclipse is an open-source software framework written primarily in Java. ... NetBeans refers to both a platform for the development of Java desktop applications, and an integrated development environment (IDE) developed using the NetBeans Platform. ... Windows Explorer running on Windows Vista Windows Explorer running on Windows XP Windows Explorer is an application that is part of modern versions of the Microsoft Windows operating system that provides a graphical user interface for accessing the file systems. ... TortoiseCVS is a CVS tool for Microsoft Windows released under the GNU General Public License. ... TortoiseSVN is a Subversion client, implemented as a windows shell extension. ...


Criticisms

While Git has many technical strengths it has been criticized for its usability and documentation.[56][57]


Some specific criticisms are:

  • Poor and/or out of date tutorials.
  • Sparse man pages.
  • Failure to document arguments available for commands, or documentation by referencing another man page within a man page.
  • A focus on the needs of the central maintainer rather than the needs of individual contributors.
  • Excessive and unnecessary complexity.
  • Occasional inconsistency between behavior of important commands.
  • Failure to provide the breadth of features that a more mature version control system provides.

The software design itself has been criticized as well.[58]


Some of these criticisms include:

  • Poorly organized and hard to read source code.
  • No support for integration with third party programs.
  • Minimal documentation for the software API.
  • Overly modularized software functions, at the expense of clarity and simplicity of design.
  • Poor (not native) Windows support.

See also

Free software Portal

Image File history File links Free_Software_Portal_Logo. ... It has been suggested that this article or section be merged with Comparison of revision control software. ... The following tables compare general and technical information for notable revision control and software configuration management (SCM) software. ...

References

  1. ^ Junio C Hamano (2008-05-28). [ANNOUNCE] GIT 1.5.5.3. git mailing list.
  2. ^ git.kernel.org - git/git.git/tree
  3. ^ Linus Torvalds (2006-05-05). Re: [ANNOUNCE] Git wiki. linux-kernel mailing list. "Some historical background" on git's predecessors
  4. ^ Linus Torvalds (2005-04-07). Re: Kernel SCM saga. linux-kernel mailing list.
  5. ^ Linus Torvalds (2005-04-08). Re: Kernel SCM saga. linux-kernel mailing list. Retrieved on 2008-02-20.
  6. ^ Linus Torvalds (2006-03-23). Re: Errors GITtifying GCC and Binutils. git mailing list.
  7. ^ Projects that use Git for their source code management. Retrieved on 2008-02-20.
  8. ^ OLPC wiki. Project hosting. Retrieved on 2008-02-20.
  9. ^ "Rails is moving from SVN to Git". Retrieved on 2008-04-03.
  10. ^ "After controversy, Torvalds begins work on git" (2005-04-19). InfoWorld. ISSN 0199-6649. 
  11. ^ GitFaq: Why the 'git' name?
  12. ^ Linus Torvalds (2006-10-19). Re: VCS comparison table. git mailing list.
  13. ^ Stenback, Johnny (2006-11-30), “bzr/hg/git performance”, Jst's Blog, <http://weblogs.mozillazine.org/jst/archives/2006/11/vcs_performance.html>. Retrieved on 20 February 2008 , benchmarking "git diff" against "bzr diff", and finding the former 100x faster in some cases.
  14. ^ Roland Dreier (2006-11-13). Oh what a relief it is., observing that "git log" is 100x faster than "svn log" because the latter has to contact a remote server.
  15. ^ Linus Torvalds (2006-10-18). Re: VCS comparison table. git mailing list., describing Git's script-oriented design
  16. ^ iabervon (2005-12-22). Git rocks!., praising Git's scriptability
  17. ^ Git User's Manual (2007-08-05).
  18. ^ Linus Torvalds (2005-04-10). Re: more git updates... linux-kernel mailing list.
  19. ^ Bruno Haible (2007-02-11). how to speed up "git log"?. git mailing list.
  20. ^ Linus Torvalds (2006-03-01). Re: impure renames / history tracking. git mailing list.
  21. ^ Junio C Hamano (2006-03-24). Re: Errors GITtifying GCC and Binutils. git mailing list.
  22. ^ Junio C Hamano (2006-03-23). Re: Errors GITtifying GCC and Binutils. git mailing list.
  23. ^ Linus Torvalds (2006-11-28). Re: git and bzr. git mailing list., on using git-blame to show code moved between source files
  24. ^ Linus Torvalds (2007-07-18). git-merge(1).
  25. ^ Linus Torvalds (2007-07-18). CrissCrossMerge.
  26. ^ Jonathan Corbet (2005-04-20), “How Tridge reverse engineered BitKeeper”, Linux Weekly News, <http://lwn.net/Articles/132938/> 
  27. ^ Linus Torvalds (2005-04-07). Re: Kernel SCM saga... linux-kernel mailing list.
  28. ^ a b c d e f Linus Torvalds. (2007, 05-03). Google tech talk: Linus Torvalds on git. Retrieved on 2007-05-16. Event occurs at 02:30.
  29. ^ Linus Torvalds (2007-06-10). Re: fatal: serious inflate inconsistency. git mailing list. A brief description of Git's data integrity design goals.
  30. ^ Linus Torvalds (2007-02-27). Re: Trivia: When did git self-host?. git mailing list.
  31. ^ Linus Torvalds (2005-04-06). Kernel SCM saga... linux-kernel mailing list.
  32. ^ Linus Torvalds (2007-02-27). Re: Trivia: When did git self-host?. git mailing list.
  33. ^ Linus Torvalds (2005-04-17). First ever real kernel git merge!. git mailing list.
  34. ^ Matt Mackall (2005-04-29). Mercurial 0.4b vs git patchbomb benchmark. git mailing list.
  35. ^ Linus Torvalds (2005-06-17). Linux 2.6.12. git-commits-head mailing list.
  36. ^ Linus Torvalds (2006-10-20). Re: VCS comparison table. git mailing list. A discussion of Git vs. BitKeeper
  37. ^ Linus Torvalds (2005-07-27). Meet the new maintainer.... git mailing list.
  38. ^ Junio C Hamano (2005-12-21). ANNOUNCE: GIT 1.0.0. git mailing list.
  39. ^ Linus Torvalds (2005-04-10). Re: more git updates.... linux-kernel mailing list.
  40. ^ Linus Torvalds (2006-03-23). Re: Errors GITtifying GCC and Binutils. git mailing list.
  41. ^ Stenback, Johnny (2006-11-30), “bzr/hg/git performance”, Jst's Blog, <http://weblogs.mozillazine.org/jst/archives/2006/11/vcs_performance.html>. Retrieved on 20 February 2008 
  42. ^ Shawn Pearce (2006-10-24). Re: VCS comparison table. git mailing list.
  43. ^ Johannes Schindelin (2007-01-01). Re: [PATCH] Speedup recursive by flushing index only once for all. git mailing list.
  44. ^ Shawn O. Pearce (2007-09-18). [PATCH 0/5] More builtin-fetch fixes. git mailing list.
  45. ^ Kevin Smith (2005-2005-06-28). Re: git 0.99.7b doesn't build on Cygwin. git mailing list.
  46. ^ Git on MSYS.
  47. ^ WinGit.
  48. ^ Johannes Schindelin (2007-10-14). Re: Switching from CVS to GIT. git mailing list. A subjective comparison of Git under Windows and Linux on the same system.
  49. ^ Martin Langhoff (2007-10-15). Re: Switching from CVS to GIT. git mailing list. Experience running msysgit on Windows
  50. ^ Johannes Sixt (2007-10-15). Re: Switching from CVS to GIT. git mailing list.
  51. ^ POSIX fork().
  52. ^ Reed, J. Paul (2006-11-27), “Version Control System Shootout Redux”, preed's blah-blah-blahg, <http://weblogs.mozillazine.org/preed/2006/11/version_control_system_shootou.html>. Retrieved on 20 February 2008 
  53. ^ SASADA, Koichi (2006-11-07). merge YARV into Ruby. ruby-core mailing list. Retrieved on 2008-02-20.
  54. ^ “WindowsInstall”, Git Wiki, <http://git.or.cz/gitwiki/WindowsInstall>. Retrieved on 20 February 2008 
  55. ^ Johannes Schindelin (2006-03-02). Re: windows problems summary. git mailing list.
  56. ^ http://changelog.complete.org/posts/594-More-on-Git,-Mercurial,-and-Bzr.html "More on Git, Mercurial, and Bzr" by John Goerzen
  57. ^ http://thunk.org/tytso/blog/2007/03/24/git-and-hg/ "Git and hg" by Ted Tso
  58. ^ http://pcapriotti.wordpress.com/2007/10/08/some-thoughts-on-git/ "Some Thoughts On Git" by Paolo Capriotti.

2008 (MMVIII) is the current year, a leap year that started on Tuesday of the Anno Domini (or common era), in accordance with the Gregorian calendar. ... is the 148th day of the year (149th in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 125th day of the year (126th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... April 7 is the 97th day of the year in the Gregorian calendar (98th in leap years). ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 98th day of the year (99th in leap years) in the Gregorian calendar. ... 2008 (MMVIII) is the current year, a leap year that started on Tuesday of the Anno Domini (or common era), in accordance with the Gregorian calendar. ... is the 51st day of the year in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 82nd day of the year (83rd in leap years) in the Gregorian calendar. ... 2008 (MMVIII) is the current year, a leap year that started on Tuesday of the Anno Domini (or common era), in accordance with the Gregorian calendar. ... is the 51st day of the year in the Gregorian calendar. ... 2008 (MMVIII) is the current year, a leap year that started on Tuesday of the Anno Domini (or common era), in accordance with the Gregorian calendar. ... is the 51st day of the year in the Gregorian calendar. ... 2008 (MMVIII) is the current year, a leap year that started on Tuesday of the Anno Domini (or common era), in accordance with the Gregorian calendar. ... is the 93rd day of the year (94th in leap years) in the Gregorian calendar. ... ISSN, or International Standard Serial Number, is the unique eight-digit number applied to a periodical publication including electronic serials. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 292nd day of the year (293rd in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 317th day of the year (318th in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 291st day of the year (292nd in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 356th day of the year (357th in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 217th day of the year (218th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 100th day of the year (101st in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 42nd day of the year in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 60th day of the year (61st in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 83rd day of the year (84th in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 82nd day of the year (83rd in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 332nd day of the year (333rd in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 199th day of the year (200th in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 199th day of the year (200th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... April 7 is the 97th day of the year in the Gregorian calendar (98th in leap years). ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 136th day of the year (137th in leap years) in the Gregorian calendar. ... Linus Benedict Torvalds ( ; ; born December 28, 1969 in Helsinki, Finland) is a Finnish software engineer best known for initiating the development of the Linux kernel. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 161st day of the year (162nd in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 58th day of the year in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 96th day of the year (97th in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 58th day of the year in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 107th day of the year (108th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 119th day of the year (120th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 168th day of the year (169th in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 293rd day of the year (294th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 208th day of the year (209th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 355th day of the year (356th in leap years) in the Gregorian calendar. ... Year 2005 (MMV) was a common year starting on Saturday (link displays full calendar) of the Gregorian calendar. ... is the 100th day of the year (101st in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 82nd day of the year (83rd in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 297th day of the year (298th in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 1st day of the year in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 261st day of the year (262nd in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 287th day of the year (288th in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 288th day of the year (289th in leap years) in the Gregorian calendar. ... Year 2007 (MMVII) was a common year starting on Monday of the Gregorian calendar in the 21st century. ... is the 288th day of the year (289th in leap years) in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... is the 311th day of the year (312th in leap years) in the Gregorian calendar. ... 2008 (MMVIII) is the current year, a leap year that started on Tuesday of the Anno Domini (or common era), in accordance with the Gregorian calendar. ... is the 51st day of the year in the Gregorian calendar. ... Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ... -1...

External links

Wikibooks
Wikibooks has a book on the topic of
Image File history File links Wikibooks-logo-en. ... Wikibooks logo Wikibooks, previously called Wikimedia Free Textbook Project and Wikimedia-Textbooks, is a wiki for the creation of books. ... LWN.net is a computing news site with an emphasis on Free/Libre/Open-Source Software and software for Unix-like operating systems. ...

  Results from FactBites:
 
git(1) (2501 words)
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.
The git concepts chapter of the user-manual and the gitcore-tutorial(7)[Core tutorial] both provide introductions to the underlying git architecture.
The current git nurse is Junio C Hamano .
Tudor Hulubei » GNU Interactive Tools (4598 words)
GIT is now able to correctly restore the terminal foreground and background under X. The previous version had a problem with this because there is no way to find out the terminal colors at startup.
GIT doesn't wait any longer for a key to be pressed after the 'fg' command is entered at the shell prompt.
GIT can be used to increase the speed and efficiency of copying and moving files and directories, invoking editors, compressing and uncompressing files, creating and expanding archives, compiling programs, sending mail and more.
  More results at FactBites »


 
 

COMMENTARY     


Share your thoughts, questions and commentary here
Your name
Your comments

Want to know more?
Search encyclopedia, statistics and forums:
 


Lesson Plans | Student Area | Student FAQ | Reviews | Press Releases |  Feeds | Contact
The Wikipedia article included on this page is licensed under the GFDL.
Images may be subject to relevant owners' copyright.
All other elements are (c) copyright NationMaster.com 2003-5. All Rights Reserved.
Usage implies agreement with terms, 1022, m