From da240343317e8eabc0d8534c109aa88b10aa6fa4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 7 Jun 2021 11:53:25 -0400 Subject: [PATCH] comment --- ...ment_3_d30a515103d04fd966aadee7f141aeee._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/significant_performance_regression_impacting_datal/comment_3_d30a515103d04fd966aadee7f141aeee._comment diff --git a/doc/bugs/significant_performance_regression_impacting_datal/comment_3_d30a515103d04fd966aadee7f141aeee._comment b/doc/bugs/significant_performance_regression_impacting_datal/comment_3_d30a515103d04fd966aadee7f141aeee._comment new file mode 100644 index 0000000000..e59b347f7e --- /dev/null +++ b/doc/bugs/significant_performance_regression_impacting_datal/comment_3_d30a515103d04fd966aadee7f141aeee._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-06-07T15:49:51Z" + content=""" +Also worth saying: When I have a choice between a bug fix and a performance +change, I kind of have to pick the bug fix. +[[bugs/indeterminite_preferred_content_state_for_duplicated_file]] was a +longstanding bug that could cause *very* expensive misbehavior. The only +way to fix it that would not have an on performance would be to +remove include= and exclude= from the preferred content expression syntax, +which would prevent a lot of current uses of preferred content. +"""]]