aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--TODOs.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/TODOs.md b/TODOs.md
index 9b2c76a..17b95ee 100644
--- a/TODOs.md
+++ b/TODOs.md
@@ -204,10 +204,29 @@ part of the first version:
- <input type="checkbox" disabled checked /> bitbucket: [`2c5e8e11a26a9a09cbeb2ceda1ca7b4e4f3aa68a`](https://git.euandreh.xyz/git-permalink/commit/?id=2c5e8e11a26a9a09cbeb2ceda1ca7b4e4f3aa68a)
- <input type="checkbox" disabled checked /> <del>generic cgit?</del> No, people should use `git-permalink.template-file-commit` and `git-permalink.template-commit-file` instead
+
# Bugs
+
# Improvements
+
+# Decisions
+
+## DONE Commit the generated manpage translations directly into the repository {#decision-1f7db3d5-002e-515e-f209-0d0917228359}
+- DONE in 2021-06-21
+
+---
+
+This is an anti-pattern in the viewpoint of the category of files that should exist in the repository, but this is made strictly for one rule: reducing the dependencies of the project for users (and not for developers), namely, gettext.
+
+Since gettext itself isn't standard (see [discussion] on this topic), adding this requirement to the consumer (user of packager) isn't desirable.
+
+So here I'm optimizing for more things being commited in the repository in the name of less requirements.
+
+[discussion]: https://www.austingroupbugs.net/view.php?id=1122
+
+
# Questions
## DONE Is an empty blank line in groff the same as a `.P` request? {#question-e3b7748d-2e67-b60b-e966-ad80c754ea58}