From 20e3eb7f541afcca454272440e305fa6822488d3 Mon Sep 17 00:00:00 2001 From: memeplex Date: Sat, 8 Jul 2017 15:47:47 +0000 Subject: Added a comment --- .../comment_3_c1f34ec908d7c4ad05c4360e29e68fb4._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Best_way_to_remove_old_version_of_specific_file/comment_3_c1f34ec908d7c4ad05c4360e29e68fb4._comment diff --git a/doc/forum/Best_way_to_remove_old_version_of_specific_file/comment_3_c1f34ec908d7c4ad05c4360e29e68fb4._comment b/doc/forum/Best_way_to_remove_old_version_of_specific_file/comment_3_c1f34ec908d7c4ad05c4360e29e68fb4._comment new file mode 100644 index 000000000..6fd7012d4 --- /dev/null +++ b/doc/forum/Best_way_to_remove_old_version_of_specific_file/comment_3_c1f34ec908d7c4ad05c4360e29e68fb4._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="memeplex" + avatar="http://cdn.libravatar.org/avatar/84a611000e819ef825421de06c9bca90" + subject="comment 3" + date="2017-07-08T15:47:47Z" + content=""" +I mean, as I understand it I unlock the file, modify it, re-add it, commit, go to the previous revision and drop the annexed old version there. I see this as an instance of the remove-old-annexed-version general case, which AFAIK is valid. What am I missing here? Should I lock instead of adding the new file? +"""]] -- cgit v1.2.3