<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<title></title>
<style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<p>Hi Wilawar,</p>
<p>For starters I can once again say that your formatting causes your emails to be hard to read; please see other messages on the <em>mailing-list</em> for further information.</p>
<p>If you want aid in how to format your replies, just ask in <code>#videolan</code> (though I am not sure how much more information can be given on the topic).</p>
<p>On 2016-12-13 17:08, Wilawar wrote:</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> I hope the format I’ve chosen this time will be more readable to
you. Let me know whether you’re interested in proof-reading plain
English at all.</code></pre>
</blockquote>
<p>Fixing grammatical errors can of course be addressed by submitting a relevant patch to <code>vlc-devel</code>. I am also not sure what you mean by “copying out the patch”; <code>git am</code> works with emails just fine, especially given that that is what it is designed to work with.</p>
<p>See the below linked resource for more information:</p>
<ul>
<li>https://git-scm.com/docs/git-am</li>
</ul>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> I also hope that you understand that I neither think this could have
been handled by RFC patches in any sensible way nor that I really
want to go through copying out the patch, creating a file for it,
applying it in Git (especially since it won’t necessarily apply on
its own as it’s part of a series), followed by eight turns of
changing a few characters (once for every change), doing a
format-patch, copying it over and wrapping it up, then sending an
eight part RFC series of nitpick changes to a single patch. (Also
called spamming.) ;)</code></pre>
</blockquote>
<p>If your email client does not support downloading the emails in an easy manner, I would recommend checking out the <em>bundle</em> feature at <code>patches.videolan.org</code>.</p>
<p>Below is a bundle that I created for the relevant patches (notice the <em>“Download bundle as email”</em> at the very top):</p>
<ul>
<li>https://patches.videolan.org/bundle/FilipRoseen-refp/tguillem-opengl/</li>
</ul>
<p><code>git</code> is a marvelous tool, and doing what you describe is not complicated at all.</p>
<ol style="list-style-type: decimal">
<li><code>git am</code> the bundles</li>
<li>Change what you want to change</li>
<li>Commit your changes (in relevant, individual, commits)</li>
<li><code>git format-patch</code></li>
<li>Reply to the relevant patches on <code>vlc-devel</code> with your patches as attachment.</li>
</ol>
<p>There is no point complaining about the workflow, we all do it; and the only one really complaining about it (for the last couple of months) are you.</p>
</body>
</html>