From 19fdf55a0bfe6a4fbcdb59b43a8fb719cf8a2923 Mon Sep 17 00:00:00 2001
From: CandyAngel <CandyAngel@web>
Date: Thu, 15 Oct 2015 10:59:59 +0000
Subject: [PATCH] Added a comment

---
 .../comment_2_fe83c600e080131b3109fe616940a25e._comment  | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 doc/walkthrough/renaming_files/comment_2_fe83c600e080131b3109fe616940a25e._comment

diff --git a/doc/walkthrough/renaming_files/comment_2_fe83c600e080131b3109fe616940a25e._comment b/doc/walkthrough/renaming_files/comment_2_fe83c600e080131b3109fe616940a25e._comment
new file mode 100644
index 0000000000..7afbd1e03a
--- /dev/null
+++ b/doc/walkthrough/renaming_files/comment_2_fe83c600e080131b3109fe616940a25e._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="CandyAngel"
+ subject="comment 2"
+ date="2015-10-15T10:59:59Z"
+ content="""
+*migrate* takes the *--force* option (introduced 5.20150327), allowing you to migrate files to the backend they are already using, but using the new extension. It was actually added for this use case!
+
+This may still incur a hash of the file though as, I believe, *migrate* will check the file at the old key is valid. You will also end up with 2 versions of the file in .git/annex/objects though (you can clean it up with *unused*).
+"""]]