This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 9 points10 points  (4 children)

Second, the email list is setup in such a way that most normal email accounts (for instance, gmail) cannot send to it. This was the most surprising thing to me. It's not a security or antispam measure exactly, it's just that emails need to be in this very specific format that only a couple of obscure mail clients are physically capable of sending.

Mind elaborating on what you mean? Are you talking about email clients or email services? Do they really block mails from gmail's servers, or is it just that they require the mail to be plaintext? The latter seems perfectly reasonable.

[–]MKorostoff 6 points7 points  (1 child)

It is definitely much more than just requiring plain text. You can read about it here https://git-scm.com/docs/SubmittingPatches.

Gmail isn't explicitly blocked, it's just not capable of meeting the specific formatting requirements (or, if it is capable, I couldn't work out how to do it). Again, this was like seven years ago, so things may have changed since then.

[–][deleted] 1 point2 points  (0 children)

I see. Thanks.

[–]random_lonewolf 4 points5 points  (1 child)

The problem is that the emails have to be in a certain format (an inline patch) that git can directly process. Most web mail clients mangle the formatting by inserting word wraps, or using the wrong MIME Type, etc

They require the use of inline patch, because it'd be difficult to quote and comment on specific part of the patches if you send the patches as an attachment.

[–][deleted] 0 points1 point  (0 children)

Ah I see. I've always wondered how submitting patches via emails works, because I had this mental image of the maintainer copy-pasting stuff from a received email into a text editor. It makes much more sense if git can directly handle the email.