Btw, the real issue here is - why do you want to make things uglier and make up stupid rules that are irrelevant to git, just for something that you admit you hadn't ever even _noticed_ until now, and now that you know about it it's not even a problem any more? especially as - we know people won't do the quoting _anyway_, since we actually have tons of examples of that in the kernel as-is. Quoting should be for _tools_, not for people. And even if we did it, we probably wouldn't be fully rfc2822-compliant anyway, because anybody sane would decide to not quote '@' and '.', rigth? Because those don't actually really have special meaning (yeah, they are "special" characters in rfc-2822, but nobody cares, and the MUA can do it for us, no)? So now we'd actually not really be rfc-compliant _anyway_, because everybody really realizes just how annoying that would really be. Linus -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Robin Lee Powell | NFS hang + umount -f: better behaviour requested. |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
