From dedaec1b9d0e846a3ffc891dd60f079380f36c65 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 16 May 2014 18:34:49 +0000 Subject: Added a comment --- .../comment_1_b3090201e90a78e049cf299fc322d60e._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups/comment_1_b3090201e90a78e049cf299fc322d60e._comment diff --git a/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups/comment_1_b3090201e90a78e049cf299fc322d60e._comment b/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups/comment_1_b3090201e90a78e049cf299fc322d60e._comment new file mode 100644 index 000000000..154bcd12e --- /dev/null +++ b/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups/comment_1_b3090201e90a78e049cf299fc322d60e._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-05-16T18:34:49Z" + content=""" +You can get the same effect by running `git annex vicfg` in 2 repositories at the same time, and adding different groups. When the repositories sync and merge, things end up in 2 groups. + +So, this is something that git-annex has to deal with being done, even if the configuration does not make sense. It deals with it by treating such a configuration the same as if the repository was in no groups, as far as preferred content is concerned. + +So, I don't see much point in adding configuration time checks, since they'd not catch all ways this can happen. +"""]] -- cgit v1.2.3