fix: cap git blockchain post excerpt
This commit is contained in:
parent
d252fa91b3
commit
78cf87b84c
@ -10,6 +10,8 @@ This article is [also published in *The FOSS Albatross.*](https://medium.com/the
|
||||
|
||||
Git today is a beloved technology developers all around the world now use to track the history of a project through revisions. Obviously, it's not magic — if you look at the hidden files in a Git repository, you'll find a `.git` folder at least as big as the rest of your repo.
|
||||
|
||||
<!-- more -->
|
||||
|
||||
But for a technology that lets you revert the exact state of your files back any number of years, that `.git` folder is surprisingly small. You'd expect that any backup program worth its salt would actually back up each version of each file, but Git tracks *changes* to files instead of the actual files themselves, a method known as [delta encoding](https://en.wikipedia.org/wiki/Delta_encoding).
|
||||
|
||||
Not to mention all of the other features that Git piles on for practically no storage cost, such as branches, merges, cherry-picking, and more?
|
||||
@ -71,4 +73,4 @@ A blockchain is nothing special. It's a technology you can use to avoid data tam
|
||||
|
||||
------
|
||||
|
||||
*SHA-1 is no longer cryptographically secure, but Git has moved to a patched version that hasn't been cracked yet. SHA-256 support is also in the works.
|
||||
*SHA-1 is no longer cryptographically secure, but Git has moved to a patched version that hasn't been cracked yet. SHA-256 support is also in the works.
|
||||
|
Loading…
Reference in New Issue
Block a user