From 37abb540e9ef07c31841fd10db79288909115fca Mon Sep 17 00:00:00 2001 From: falsifian Date: Sat, 12 Sep 2020 15:30:06 +0000 Subject: [PATCH] Added a comment --- .../comment_2_23d18b52d87468ffadf0a3e04bf8052d._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Can_I_remove_a_groupwanted_expression__63__/comment_2_23d18b52d87468ffadf0a3e04bf8052d._comment diff --git a/doc/forum/Can_I_remove_a_groupwanted_expression__63__/comment_2_23d18b52d87468ffadf0a3e04bf8052d._comment b/doc/forum/Can_I_remove_a_groupwanted_expression__63__/comment_2_23d18b52d87468ffadf0a3e04bf8052d._comment new file mode 100644 index 0000000000..c1c622e132 --- /dev/null +++ b/doc/forum/Can_I_remove_a_groupwanted_expression__63__/comment_2_23d18b52d87468ffadf0a3e04bf8052d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="falsifian" + avatar="http://cdn.libravatar.org/avatar/59c3c23c500d20d83ecb9d1f149be9ae" + subject="comment 2" + date="2020-09-12T15:30:05Z" + content=""" +Update: I've verified that the empty groupwanted expression indeed does indeed block the groupwanted expression from another group. So, other than making sure I never use the `common` group again, or some manual repository surgery, I'm not sure how to recover from this situation. +"""]]