<!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>On 2016-12-13 21:55, Wilawar wrote:</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> Formatting such as displayed there (which is, btw, also not a patch)?
https://mailman.videolan.org/pipermail/vlc-devel/2016-October/109662.html
Have a look at the author, please.</code></pre>
</blockquote>
<p>I am well aware of what messages I have sent on to <code>vlc-devel</code>, and no; that message does not include a patch. The information posted is however far more consise than what you have been doing in your replies, and the formatting is (at least in my opinion) far easier to handle.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> More precedence:
https://mailman.videolan.org/pipermail/vlc-devel/2016-October/110086.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-December/110857.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-December/110841.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-December/110790.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-December/110769.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110721.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110708.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110704.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110632.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110488.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110585.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110521.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110509.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110507.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110504.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110243.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110238.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110236.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110144.html
https://mailman.videolan.org/pipermail/vlc-devel/2016-November/110450.html</code></pre>
</blockquote>
<p>I am not sure what you want the above list of messages to tell the reader of your email, but all I see are consistently formatted emails that has not received any complaint about readability.</p>
<p>If you are talking about the fact that the replies does not include a patch, please see later segments of this email (as I am sure I will address that at one point or another).</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> I didn’t say git was too hard for me to use (do you want to imply again
that I’m stupid?),</code></pre>
</blockquote>
<p>Nor did I.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> I said it was too cumbersome and I remain at that position. If you
want to require me to use git and do the whole roundtripping dance
just to point out a few typos and English corrections, I plainly
won’t do that – which I feel like might be your true intent anyways.</code></pre>
</blockquote>
<p>No one said that you <strong>had</strong> to respond to a patch that way. My reply was simply saying that it is certainly possible to reply using that mechanism, and that the workflow is not overly complicated.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> Also, please leave the strawmans on the fields, no need to beat them up.</code></pre>
</blockquote>
<p>No comment.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> Then, I don’t get why you tell me to ask about formatting on the IRC
channel when we talked about precisely this topic a few days ago and
you were unwilling to give me more information back then – did you
change your mind? If so, why do you still tell me to go looking
through other mail?</code></pre>
</blockquote>
<p>Unwilling to give you information? That seems a bit harsh given that I have been trying to help you with your formatting issues ever since your first message to <code>vlc-devel</code> (and not just in-regards of emails).</p>
<ul>
<li>https://mailman.videolan.org/pipermail/vlc-devel/2016-August/109065.html</li>
</ul>
<p>I have been telling you to look at other mails on the mailing-list given that these have not received the same sort of feedback as the ones you are sending.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> After the topic had been raised, I’ve explicitly looked for
formatting differences when I went through new messages on this
list. I’ve noticed only two obvious differences: First, that many of
you seem to end your lines either at around 80 or at around 72
characters (as defined in some old advice) and second, that you seem
to introduce many small paragraphs for no apparent reason.</code></pre>
</blockquote>
<p>I think the above speaks for itself.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> On this list, there doesn’t seem to be any hard limit on line length
(there are also a couple of guys who use different lengths). It’s
not really necessary either in this day and age, so I assumed it was
just an old habit. If you wanted me to adhere to a limit of 72
characters (80 doesn’t really make sense IIUC), you could have told
me straight into my virtual face, right around the first time when I
asked about formatting on the ML; I believe I even mentioned
line-length explicitly (no, I won’t bother looking it up, I’ve
already wasted enough time on this mail …).</code></pre>
</blockquote>
<p>It is not an old habit, mailing-lists in general follow the same (sometimes unwritten) guidelines as the one we have on <code>vlc-devel</code>, for several different reasons.</p>
<p>One of them being that since many of the messages on <code>vlc-devel</code> contains patches, <code>monospace</code> rendering are used consistently (which is the major problem with the formatting you are sending your emails as).</p>
<p>If you would like to have an alternative view of the message you are sending, do what I do and send both <code>text/plain</code> and <code>text/html</code> (or whatever it is that you prefer). Please, do not expect clients to render <code>text/plain</code> with a proportional font (as you recently implied on IRC).</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> If, for some reason, it would help you with reading if I inserted an
empty line every two sentences (this honestly seems to be the
average case), I’d be willing to do that, although I dislike this
style myself.</code></pre>
</blockquote>
<p>It is not limited to insertions of empty lines, but that could certainly help in some of the scenarios.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> With all this said, I do take Thomas’ feedback seriously. I do not
see any place where I’ve been overly verbose – the information which
I thought should be there is there, no part is really superfluous –
except maybe the very first sentence (the one about my original
intent when writing this message), I could have omitted that one.</code></pre>
</blockquote>
<p>I will let someone else reply to this part given that you are now implying (over IRC) that my opinion is one of a kind, and that no one besides me see the issues I’ve previously described.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> I do not want to leave out the reasoning for changes (which was also
relatively short), especially when they are about language, a very
personal matter that is highly dependent on style and preference.</code></pre>
</blockquote>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> I will read my previous mail again tomorrow, to get a more unbiased look
on it, but I don’t expect to gain much
from doing this, it didn’t help with my other mails in the past.</code></pre>
</blockquote>
<p>Sounds good to me!</p>
<p>Best Regards,<br />
Filip</p>
</body>
</html>