remove old closed bugs and todo items to speed up wiki updates and reduce size
Remove closed bugs and todos that were last edited or commented before 2020. Except for ones tagged projects/* since projects like datalad want to keep around records of old deleted bugs longer. Command line used: for f in $(grep -l '|done\]\]' -- ./*.mdwn); do if ! grep -q "projects/" "$f"; then d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2020 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2020 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; fi; done for f in $(grep -l '\[\[done\]\]' -- ./*.mdwn); do if ! grep -q "projects/" "$f"; then d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2020 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2020 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; fi; done
This commit is contained in:
parent
4eb3778aec
commit
a6a6217322
1141 changed files with 1 additions and 32370 deletions
|
@ -4,7 +4,7 @@ now when the security hole is disclosed.
|
|||
Security is not compositional. You can have one good feature, and add
|
||||
another good feature, and the result is not two good features, but a new
|
||||
security hole. In this case
|
||||
[[bugs/security_hole_private_data_exposure_via_addurl]] (CVE-2018-10857).
|
||||
[[security/CVE-2018-10857_and_CVE-2018-10859|CVE-2018-10857]].
|
||||
And it can be hard to spot this kind of security hole, but then once it's
|
||||
known it seems blindly obvious.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue