From 01331f0b8f45325944cb6b6710985df986dbba76 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 25 May 2021 10:04:29 -0400 Subject: [PATCH] required content update --- .../comment_10_f57e3d77a0ee6a504fa9cb404ab7a681._comment | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_10_f57e3d77a0ee6a504fa9cb404ab7a681._comment b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_10_f57e3d77a0ee6a504fa9cb404ab7a681._comment index 657b116505..6773c32371 100644 --- a/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_10_f57e3d77a0ee6a504fa9cb404ab7a681._comment +++ b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_10_f57e3d77a0ee6a504fa9cb404ab7a681._comment @@ -6,4 +6,13 @@ There must also be the same problem for required content, and that should also be fixed. Will be easy to do once the information is gathered into the keys database. + +Actually, in the drop --auto case, required content is automatically +handled correctly, because when checking preferred content it also checks +required content. + +However, drop without --auto normally honors required content, but if the +same content is used by 2 files, one required and the other not, dropping +the latter file will drop the content of the first, violating required +content settings. This seems like it ought to be fixed. """]]