Fine-tune that shallow-clone recommendation.

This commit is contained in:
Steven Black
2017-04-08 23:01:33 -04:00
parent 4e1238dd6f
commit be17527117
17 changed files with 18 additions and 28 deletions
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
+2 -12
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.
@@ -12,16 +12,6 @@ This repository consolidates several reputable `hosts` files, and merges them
into a unified hosts file with duplicates removed. This repo provides several
hosts files tailored to you need to block.
<div class="blankslate blankslate-large">
<img class="avatar left" src="https://avatars0.githubusercontent.com/u/80144?v=3&s=50" width="50" height="50">
<h3>Shallow clone and avoid 400 Mb of history</h3>
<p>I recommend a **shallow clone** because you probably don't need many years of history.</p>
<p>Like this:</p>
<pre>
git clone --depth 5 https://github.com/StevenBlack/hosts.git
</pre>
</div>
* Last updated: **April 09 2017**.
* Here's the [raw hosts file with base extensions](https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts) containing 35,460 entries.
@@ -327,4 +317,4 @@ devices under a variety of operating systems.
* [Block ads and malware via local DNS server](https://github.com/mueller-ma/block-ads-via-dns "Block ads and malware via local DNS server") (for Debian, Raspbian & Ubuntu): Set up a local DNS server with a `/etc/bind/named.conf.blocked` file, sourced from here.
* [Blocking ads and malwares with unbound](https://deadc0de.re/articles/unbound-blocking-ads.html "Blocking ads and malwares with unbound") – [Unbound](https://www.unbound.net/ "Unbound is a validating, recursive, and caching DNS resolver.") is a validating, recursive, and caching DNS resolver.
* [Blocking ads and malwares with unbound](https://deadc0de.re/articles/unbound-blocking-ads.html "Blocking ads and malwares with unbound") – [Unbound](https://www.unbound.net/ "Unbound is a validating, recursive, and caching DNS resolver.") is a validating, recursive, and caching DNS resolver.
+1 -1
View File
@@ -1,4 +1,4 @@
#### Cloning? Use a shallow clone and avoid 400 Mb of history
### Cloning? Use a shallow clone and avoid 400 Mb of history
A **shallow clone** is a good idea because you probably don't need many years of history.