Pro Git

Chacon, S., & Straub, B. (2014). Pro Git. Apress.

Type

Book

Intellectual base

Review or monograph

Year

2014

DOI

10.1007/978-1-4842-0076-6

ISBN

9781484200773

Link

https://link.springer.com/book/10.1007/978-1-4842-0076-6

Cited from

biology_ecology, computer_science, history_historiography, information_theory, mathematics, systems_cybernetics

Cited by

7 citations across 7 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Branching and Merging
  • Branching and merging is the structural pattern in which a single lineage diverges into parallel, independently-evolving variants and those variants are later reconverged — selectively recombined back into a shared line — rather than developing in a single unbranched sequence.

    This sourceApress. Canonical reference on distributed version control: establishes the fork-and-merge cycle as the central organizing primitive of collaborative development, the expectation that divergent branches reconverge into a shared line, and the three-way merge (common ancestor plus two branch tips) as the standard realization of the pattern.

• Contraposition
  • Because the consequence space a single module would produce is far smaller than the cause space of "where could this failure live," each such absence-of-consequence check eliminates a whole block of candidate causes at once — the same logarithmic pruning that makes git bisect and binary search through a commit history effective

    This sourceDocuments `git bisect` as binary search through commit history: 'if the bug existed at commit C, the test would fail at C; the test passes at C, so the bug is not in that prefix' — the contrapositive elimination giving logarithmic pruning.

• Directed Acyclic Graph
  • Version control encodes commit history as a DAG in which merges combine parents but history never loops.

    This sourceGit models commit history as a directed acyclic graph in which merges join parents but history never loops.

• Immutability
  • The identity of a commit is its content, so any change necessarily produces a different commit.

    This sourceApress. Canonical reference on distributed version control: establishes the fork-and-merge cycle as the central organizing primitive of collaborative development, the expectation that divergent branches reconverge into a shared line, and the three-way merge (common ancestor plus two branch tips) as the standard realization of the pattern.

• Memory Consolidation
  • And in software a working-tree change is the fragile trace, while commit-then-test-then-merge is the consolidation process that joins it to the durable repository state.

    This sourceDescribes the version-control model in which a fragile working-tree change becomes durable only when committed and merged into the repository's durable history—the commit-then-merge cycle as a consolidation process.

• Identity-Preserving Modification
  • In software engineering, a file is edited or a record updated in place, and version-control systems distinguish modification (a change on the same path) from rename (a path change detected by similarity) from delete-plus-add (broken identity).
• Two-Store Architecture
  • The same structure governs version control, where the working tree and staging index (fast) couple to commit history (slow) through the deliberate, user-initiated transfer window of a commit.

    This sourceDescribes the working tree, staging index, and commit history, with the commit as a deliberate user-initiated transfer.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 2 other ways.

• https://git-scm.com/book/en/v2 ×4
• https://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git ×1

Registry ID ref:408942eef02d · see in the full table