summaryrefslogtreecommitdiff
path: root/content/posts/removing-files-from-git-history.md
diff options
context:
space:
mode:
authorChristoph Cullmann <cullmann@kde.org>2019-04-15 20:07:10 +0200
committerChristoph Cullmann <cullmann@kde.org>2019-04-15 20:07:10 +0200
commit5e699a92c89d35e74fcb4c513591d32af008d30f (patch)
treecefe142be9dd85721adf0186fd320c1209f98d7b /content/posts/removing-files-from-git-history.md
parent6188e08eb298ea7f8f6522b8c00770ba1b21f7d3 (diff)
nicer format
Diffstat (limited to 'content/posts/removing-files-from-git-history.md')
-rw-r--r--content/posts/removing-files-from-git-history.md4
1 files 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.**