diff options
| author |  memeplex <memeplex@web> | 2017-07-08 15:47:47 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-07-08 15:47:47 +0000 |
| commit | 20e3eb7f541afcca454272440e305fa6822488d3 (patch) | |
| tree | 302898a149f86a6477a0320ac0c64781e7c7bba5 | |
| parent | a0270fe3d0ce10fa21ed058545c37e67532a71b3 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Best_way_to_remove_old_version_of_specific_file/comment_3_c1f34ec908d7c4ad05c4360e29e68fb4._comment | 8 |
1 files changed, 8 insertions, 0 deletions
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? +"""]] |