From eed0931ace36136199be6c7396277fd7e04c4621 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 4 Feb 2015 16:07:54 -0400 Subject: [PATCH] comment --- ...ent_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/wishlist:_use_hardlinks_for_local_clones/comment_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment diff --git a/doc/todo/wishlist:_use_hardlinks_for_local_clones/comment_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment b/doc/todo/wishlist:_use_hardlinks_for_local_clones/comment_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment new file mode 100644 index 0000000000..69dc0a6cee --- /dev/null +++ b/doc/todo/wishlist:_use_hardlinks_for_local_clones/comment_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2015-02-04T20:03:19Z" + content=""" +No, please don't wrap your `cp`. Forcing git-annex to hard link +files like that can result in data loss, in a number of different +scenarios. And it's generally asking for a broken system. + +Since version 5.20140915, you can "git clone --shared" and +this will set up a clone of a repository in which git-annex will +use hardlinks, in a safe and reliable way. (Notably it marks the clone +as untrusted.) +"""]]