> a consensus on how to proceed here might be useful for documenting best
practices as other apps run into similar troubles.
I guess I'd suggest...
Most realistic in immediate future: Accept it as a current limitation
(possibly handle TooManyFieldsSent)
Someday later, perhaps: Allow a "select e
I agree with Reinout and on the use of the present tense, so a commit
message would read:
"Adds password validation to prevent the usage of ..."
My mind finds this way easier to understand than: "Add password validation
..."
Wim
On Monday, 27 June 2016 13:55:54 UTC+2, Daniele Procida wrote:
>
