From 52b0a6530d68a3667649b1c26484b2c6f59ebdfe Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Mon, 14 Oct 2019 03:42:05 +0000 Subject: [PATCH] Added a comment: getting v5 semantics --- .../comment_15_3725ed643660d0e1b8fadd17705aebf1._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/lets_discuss_git_add_behavior/comment_15_3725ed643660d0e1b8fadd17705aebf1._comment diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_15_3725ed643660d0e1b8fadd17705aebf1._comment b/doc/forum/lets_discuss_git_add_behavior/comment_15_3725ed643660d0e1b8fadd17705aebf1._comment new file mode 100644 index 0000000000..6ae8603b5d --- /dev/null +++ b/doc/forum/lets_discuss_git_add_behavior/comment_15_3725ed643660d0e1b8fadd17705aebf1._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="getting v5 semantics" + date="2019-10-14T03:42:05Z" + content=""" +The best way to restore v5 semantics right now seems to be: (1) set `annex.largefiles=nothing` to prevent `git add` from annexing; (2) make an alias to use instead of `git annex add`, which temporarily sets `annex.largefiles` to whatever it normally would be and then calls `git-annex-add`. But old scripts that call `git-annex-add` would need to be changed to call the alias. +"""]]