From 572aa58a50427f39d7b6dfffb4e87052778c574a Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Tue, 13 Dec 2022 14:15:28 +0000 Subject: [PATCH] Added a comment: why othertmp to be on the same file system? --- ...nt_17_df13b7e66963a6d2673e49f52afb978a._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/internals/comment_17_df13b7e66963a6d2673e49f52afb978a._comment diff --git a/doc/internals/comment_17_df13b7e66963a6d2673e49f52afb978a._comment b/doc/internals/comment_17_df13b7e66963a6d2673e49f52afb978a._comment new file mode 100644 index 0000000000..c750a92392 --- /dev/null +++ b/doc/internals/comment_17_df13b7e66963a6d2673e49f52afb978a._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="why othertmp to be on the same file system?" + date="2022-12-13T14:15:28Z" + content=""" +Joey, you said + +> .git/annex/othertmp has to be on the same filesystem as the work tree and git repository. + +is that for atomic/quick renames important for adjusted branch unlocked mode? asking because in datalad we have that \"wreckless\" mode where we symlink an entire `.git/annex` from original clone to e.g. have quick throw away clone to access the data and possibly even without modifying state of any annexed key. + +Or how else are we stepping on the shovel here? +"""]]