[MTOS-dev] Suggestion for patch communication/application

[Jay Allen]

Hi all,

I'd like to brainstorm with you all for a second about how we can
streamline the communication and application of proposed patches. For
me at least, receiving patchfile sources in email is less than optimal
for a few reasons:

 * Line wrapping in "certain popular mail clients" requires
reconstruction of the patch
 * Copy/pasting from email and subsequent creation of a local patch
file is inefficient

While using email attachments (if even allowed on this list) is one
possible solution for the former, it still takes too many steps for my
liking (saving the attachment to my HD, switching to shell to apply
the patch, etc).

If I am correct that most of us apply patches via shell, it would seem
like the best location for the patch would be on the web where one
could use curl to grab the source and pipe that output into the patch
utility.  In that case, saving the patch on your webserver or using
something like http://pastie.org/ would work well.

But perhaps there's a better workflow?  I'd love to hear some of your
thoughts on the subject either on efficiency under the current
environment or other ideas for improving the system.

-- 
Jay Allen
Endevver Consulting
415-200-6985