✳flâneur — a map of the web's best reading

Disaster Recovery with Git

web.mit.edu · 1,860 words · saved by 1 readers

We’ve defined a commit as a snapshot of our entire project, but if you ask Git, it doesn’t seem to see things that way: Git is assuming that most of our project does not change in any given commit, so showing only the differences will be more useful. Almost all the time, that’s true. But we can also use Git to show us the entire state of the repository at a particular commit, not just the differences. We can ask Git to show us what was in a particular file at a particular commit by typing a colon : after the commit ID and specifying a path to that file: We can also use this command to show the contents of a particular folder at a given commit by specifying a path to that folder. Notably, we can show the state of the entire repo at a given commit by typing nothing after the colon: As the empty filepath corresponds to the root directory in the repo and thus shows all the files in the repo. Using git show is one of the simplest ways you can use Git to recover from a disaster: ask Git to g

Disaster Recovery with Git Disaster Recovery with Git Objectives Understand how to view and retrieve old versions from Git using Git commands Practice using Git to recover old versions of code Why do commits look like diffs? We’ve defined a commit as a snapshot of our entire project, but if you ask Git, it doesn’t seem to see things that way: $ git show 1255f4e commit 1255f4e4a5836501c022deb337fda3f8800b02e4 Author: Max Goldman <maxg@mit.edu> Date: Mon Sep 14 14:58:40 2015 -0400 Change the greeting diff --git a/hello.txt b/hello.txt index c1106ab..3462165 100644 --- a/hello.txt +++ b/hello.txt

Explore this link on the map →

related reading