Skip to contentSkip to conversation

update SubmittingPatches to clarify attachment policy

RFC PATCH Bodo Eggert <[email protected]> 1 participant 1 message May 5, 2005 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 8 lines · Dmitry Torokhov
Quoted 4 lines · Dave Hansen

I think the general opinion of posting patches as attachments has changed over the last few years. Mailers have been getting a lot better at handling them, even quoting non-message-body plain/text attachments in replies.

What, Linus updated his pine?????

Pine is usurally better for handling patches than other mailers. In pine, you can save a message into a mbox using very few keystrokes, and if the patches are not encoded, patch can parse them from there.

BTW: I wrote a tool for handling MIME mails. Originally it was intended to catch spam in procmail, but it can safe the individual parts into seperate files, too. Maybe this is usefull:

http://7eggert.dyndns.org/~7eggert/hp/l/spam+mail/mime-analyzer/

(You'd use "cd $destdir && formail < $mbox -s mail-analyzer -copy_all -")

Signature · 1 line
According to my calculations the problem doesn't exist.