On 11 Feb 2022, at 15:00, Chuck Lever III wrote:
On Feb 11, 2022, at 2:30 PM, Benjamin Coddington
<bcodding@xxxxxxxxxx> wrote:
All the arguments for exacting tolerances on how it should be named
apply
equally well to anything that implies its output will be used for nfs
client
ids, or host ids.
I completely disagree with this assessment.
But how, and in what way? The tool just generates uuids, and spits them
out, or it spits out whatever's in the file you specify, up to 64 chars.
If
we can't have uuid in the name, how can we have NFS or machine-id or
host-id?
I object strongly to the name nfsuuid, and you seem to be inflexible.
This
is not a hill I want to die on, however I reserve the right to say "I
told
you so" when it turns out to be a poor choice.
How does agreeing with you multiple times in my last response and making
further suggestions for names seem inflexible to you? This is the worst
part of working over email - I think you're misreading my good humor in
the
face of a drudging discussion as sarcasm or ill will.
Let's find the best name.. I'm still going here. I do really like
`persistychars`, but I expect that's too fun for everyone. The name at
least gets closer to your bar of describing exactly what the tool does.
I'm really tired of arguing over the name, and I'm trying my best to
keep
some good humor about it, and find something that meets everyone's
needs.
Ben
