On Fri, Jan 05, 2018 at 09:42:31PM +0100, Adam Borowski wrote:
> Thus, could someone suggest something betterer? It doesn't need to spell
> "kitteh", nor even anything cat themed, although obviously references to
> nasty things like dogs, Hitler or emacs (in decreasing order of badness)
> are
On 1/5/2018 3:42 PM, Adam Borowski wrote:
The best I've been able to come up with was: kitteh "Kill Invalid Tree
Terms, Evading Harm". This is groan-worthy, and especially "tree" is
incorrect as files/dirs/sockets/fifos/etc are at most tree nodes.
Meow!
CUTEN
Cull Undesirable Terminology &
Adam Borowski dijo [Fri, Jan 05, 2018 at 09:42:31PM +0100]:
> Hi!
> I'd like to ask for help with devising an acronym, as my ability with puns
> or other wordplay in any language is almost non-existant.
>
> Background: I'm working on a kernel facility to set a policy for filenames,
> for security
Le 5 janvier 2018 21:42:31 GMT+01:00, Adam Borowski a
écrit :
>Hi!
>I'd like to ask for help with devising an acronym, as my ability with
>puns
>or other wordplay in any language is almost non-existant.
>
>Background: I'm working on a kernel facility to set a policy for
Adam Borowski writes:
> The best I've been able to come up with was: kitteh "Kill Invalid Tree
> Terms, Evading Harm". This is groan-worthy, and especially "tree" is
> incorrect as files/dirs/sockets/fifos/etc are at most tree nodes.
Neuter Your Ambiguous Names
--
\
On Fri, 05 Jan 2018, Adam Borowski wrote:
> Thus, could someone suggest something betterer? It doesn't need to
> spell "kitteh", nor even anything cat themed, although obviously
> references to nasty things like dogs, Hitler or emacs (in decreasing
> order of badness) are unpreferred.
Makes Evil
On 05/01/18 14:42, Adam Borowski wrote:
> Background: I'm working on a kernel facility to set a policy for filenames,
> for security reasons. The recommended defaults are banning '\n' and 01..31,
> the user can also elect to ban invalid Unicode, initial and final spaces,
> initial '-', etc. The
7 matches
Mail list logo