SoylentNews is people
SoylentNews
Petter Reinholdtsen at the Skolelinux project has a very, very short blog post which simply asks if it is time for an official MIME type for patches and points to the mailing list proposed for such a discussion.
As part of my involvement in the Nikita archive API project, I've been importing a fairly large lump of emails into a test instance of the archive to see how well this would go. I picked a subset of my notmuch email database, all public emails sent to me via @lists.debian.org, giving me a set of around 216 000 emails to import. In the process, I had a look at the various attachments included in these emails, to figure out what to do with attachments, and noticed that one of the most common attachment formats do not have an official MIME type registered with IANA/IETF. The output from diff, ie the input for patch, is on the top 10 list of formats included in these emails. At the moment people seem to use either text/x-patch or text/x-diff, but neither is officially registered. It would be better if one official MIME type were registered and used everywhere.
What do Soylentils have to say for or against designating a specific MIME type for software patches? Which details need to be addressed and would there be any pitfalls?
(Score: 2) by RamiK on Sunday November 04 2018, @09:58PM (1 child)
This is one of the best features of patchwork [github.com]: It picks up patches off the mailing list and builds them automatically with a continuous integration service. Then it replies to the patch message with the results.
Outlook wise, there add-ins hooking up to git apply and git diff that can be automated to do exactly what you described on a build server that I wouldn't be surprised to find some Windows build server is actually using somewhere.
(stiff upper lip)
compiling...
(Score: 4, Funny) by tibman on Sunday November 04 2018, @10:37PM
Looks like they use text/plain : D
SN won't survive on lurkers alone. Write comments.