Ah, sorry. I see the issue. I've never written any Go before so I had
no tooling set up. I ran go fmt manually but forgot to git add the file
before amending my commit. I'm not being stubborn, just stupid; I
totally get the importance of automatic, agreed-upon formatting!
I removed my comments from the commit, but I don't really see what's
wrong with putting comments in the commit description in general. If
written in the email's comments and not the commit/patch itself, the
questions don't make it into the commit log, and are less likely to
be stumbled upon in the future. I see there are several other commits
in the log that pose questions about further refactoring, like 92f59ef.
At the very least, the rationale for the change (in this case, the fact
that emails are arriving with uppercase MIME signatures) should be
documented in the commit description, no?
I got an email the other day with an "APPLICATION/PGP-SIGNATURE"
attachment that wasn't recognized because it wasn't a lowercase
"application/pgp-signature". Perhaps MIME types should be lowercased
globally upon parsing?
This is still not properly formated.
As you've already been told:
> Please run `go fmt ./...` before sending a patch next time :)
This isn't to nag you, this is really how you should do it.
Most editors have functionality to do this automatically when you save.
Every go code on earth (at least most of it) looks the very same because everyone
uses the same formatting tool in go. You should follow suit.