Git Revision Control System

From GM-RKB
Jump to navigation Jump to search

A Git Revision Control System is a distribute revision control system (for tracking changes in source code during software development).

  • Context:
  • Example(s):
    • Git 1.0.0, released in December 2005, represents the first stable release of Git, marking the beginning of its version history.
    • Git 1.5.0, introduced in April 2007, was a significant update that transitioned Git from a collection of individual tools to a more unified software suite.
    • Git 1.6.0, rolled out in August 2008, further refined the user interface and improved performance.
    • Git 2.0.0, released in June 2014, brought changes to Git's handling of branches and included other significant improvements.
    • Git 2.28.0, released in July 2020, introduced the ability to configure the default branch name for new repositories.
  • Counter-Example(s):
  • See: GitHub Service, Fossil RCS, SCCS.


References

2023a


2023b

  • (ChatGPT OpenAI, 2023) ⇒ https://chat.openai.com/
    • Git was created by Linus Torvalds, the creator of the Linux operating system, in 2005. The primary reason for Git's creation was to handle source control for the Linux kernel, which involved many contributors and required a system that could effectively handle numerous branches of development. The goal was to create a system that was more flexible, reliable, and powerful than the systems available at that time. ...
    • … Prior to Git, the Linux kernel was maintained using a proprietary distributed revision control system called BitKeeper. In 2005, due to a dispute between the creators of BitKeeper and the Linux community, BitKeeper was no longer available for free. This situation prompted the creation of Git as a new tool built from scratch, with the objective of maintaining the Linux Kernel.

      Some of the guiding goals for Git's development were:

      • Speed: Git was designed to be fast and to perform operations like merging and branching efficiently.
      • Simple Design: Git was created to be easy to understand and to have a clean design.
      • Strong Support for Non-Linear Development: Git was designed to support thousands of parallel branches and has tools to help navigate this complexity.
      • Fully Distributed: Git was designed to support a distributed workflow, giving each developer a full local copy of the entire development history.
      • Able to Handle Large Projects: Git was created to handle large projects like the Linux kernel efficiently.

2023

  1. Torvalds, Linus (7 April 2005). "Re: Kernel SCM saga." linux-kernel (Mailing list). Archived from the original on 1 July 2019. Retrieved 3 February 2017. “So I'm writing some scripts to try to track things a whole lot faster."
  2. Torvalds, Linus (10 June 2007). "Re: fatal: serious inflate inconsistency". git (Mailing list).
  3. Linus Torvalds (3 May 2007). Google tech talk: Linus Torvalds on git. Event occurs at 02:30. Archived from the original on 28 May 2007. Retrieved 16 May 2007.
  4. "A Short History of Git". Pro Git (2nd ed.). Apress. 2014. Archived from the original on 25 December 2015. Retrieved 26 December 2015.