The umask setting can now be set to private, group, or public, avoiding the need...

[ikiwiki.git] / doc / bugs / octal_umask_setting_is_unintuitive.mdwn

diff --git a/doc/bugs/octal_umask_setting_is_unintuitive.mdwn b/doc/bugs/octal_umask_setting_is_unintuitive.mdwn
index 0a63940cef6b018fd9435bc4267f3422d03f73e8..5cdefcf09d70a7fad5eafa790571dd0629f17897 100644 (file)
--- a/doc/bugs/octal_umask_setting_is_unintuitive.mdwn
+++ b/doc/bugs/octal_umask_setting_is_unintuitive.mdwn
@@ -28,6 +28,9 @@ you have to use one of
 
 and if you try to say 022 you'll get 22 decimal = 026 octal.
 
+[[!tag patch]]
+[[!template id=gitbranch branch=smcv/umask-keywords author="[[smcv]]"]]
+
 Perhaps the best way to solve this would be to have keywords
 for the few values of `umask` that are actually useful?
 
@@ -43,3 +46,10 @@ via a symlink attack. So I don't think we need keywords
 for those.
 
 --[[smcv]]
+
+> I support this change, but your git repository does not seem to have
+> that branch (or anything) in it today. --[[Joey]]
+
+>> git pushes have a restrictive umask, ironically... fixed. --[[smcv]]
+
+>>> [[done]] --[[Joey]]