From 5e699a92c89d35e74fcb4c513591d32af008d30f Mon Sep 17 00:00:00 2001 From: Christoph Cullmann Date: Mon, 15 Apr 2019 20:07:10 +0200 Subject: [PATCH] nicer format --- content/posts/removing-files-from-git-history.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/posts/removing-files-from-git-history.md b/content/posts/removing-files-from-git-history.md index 59c5fc6..472340c 100644 --- a/content/posts/removing-files-from-git-history.md +++ b/content/posts/removing-files-from-git-history.md @@ -1,6 +1,6 @@ --- title: "Removing Files from Git History" -date: 2019-04-15T20:05:00+02:00 +date: 2019-04-15T20:07:00+02:00 draft: false categories: [git, development] tags: [git] @@ -32,4 +32,4 @@ with just to not wait potential hours for the aggressive GC. For me that was good enough to get some estimate of the later size for my experiments before I settled to some final settings and did the real run. -**And as always, if you touch your Git history: Do that only if you really need to, keep backups, check carefully that afterwards the repository is in some sensible state (`git fsck --strict` is your friend) and inform all people using that repository that they will need to do a full new clone.** +And as always, if you touch your Git history: **Do that only if you really need to, keep backups, check carefully that afterwards the repository is in some sensible state (`git fsck --strict` is your friend) and inform all people using that repository that they will need to do a full new clone.**