~sircmpwn/git-send-email.io

ref: 0.1.4 git-send-email.io/top-posting.html -rw-r--r-- 2.9 KiB
b824632eDrew DeVault Use reply["Cc"] for copying list 1 year, 7 months ago
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
<!doctype html>
<html>
  <head>
    <title>What is top-posting?</title>
    <link rel="stylesheet" type="text/css" href="index.css" />
    <meta name="viewport" content="width=device-width, initial-scale=1">
  </head>
  <body>
    <div class="container">
      <h1>What is top posting?</h1>
      <p>
        You may have heard of "top posting" and "bottom posting" in the context
        of emails. Many email clients, when replying to an email, will insert
        the entire thread thus far into the reply, leaving you to write your
        message at the top. This results in emails like this:
      </p>
      <pre>Yes, that sounds good.

Jim said on 2019-03-23 at 11:02 PM:
&gt; Are you okay with maroon?
&gt;
&gt; Tim said on 2019-03-23 at 10:43 PM:
&gt;&gt; Do we know what color we should use for the background?
&gt;&gt; 
&gt;&gt;&gt; Jim said on 2019-03-23 at 10:30 PM:
&gt;&gt;&gt; Is there anything left to do on the site?</pre>
      <p>
        This is called "top posting", and it gets out of hand pretty quickly.
        This is strongly discouraged on most mailing lists. Many people don't
        realize that you can actually edit the previous messages when composing
        your reply. A better response would be:
      </p>
      <pre>Jim said on 2019-03-23 at 11:02 PM:
&gt; Are you okay with maroon?

Yes, that sounds good.</pre>
      <p>
        Trim out the fat, only quoting what you need, and respond inline. This
        also becomes useful for clarifying what parts of a message you're
        replying to. If I received this email, for example:
      </p>
      <pre>Hey Drew,

Can you look into the bug which is causing 2.34 clients to disconnect
immediately? I think this is related to the timeouts change last week.

Also, your fix to the queueing bug is confirmed for the next release,
thanks!</pre>
      <p>
        I might reply like this:
      </p>
      <pre>Hey Sarah, I can look into that for sure.

&gt; I think this is related to the timeouts change last week.

I'm not so sure. I think reducing the timeouts would *improve* this issue,
if anything. I'll look into it.

&gt; Also, your fix to the queueing bug is confirmed for the next release,
&gt; thanks!

Sweet! Happy to help.
</pre>
      <p>
        This style is also useful for reviewing patches - quote the specific
        lines you have feedback on, and trim out everything else.
        <a
          href="https://lists.sr.ht/~emersion/mrsh-dev/%3C20190125085755.5290-1-cristianontivero%40gmail.com%3E"
          target="_blank"
        >Here's an example email thread</a> showing a simple code review that
        you can check out if you're curious.
      </p>
      <p>
        Thanks for your patience! We know that learning how to fit in with a
        new community and a new style of communication can be tough, but
        everyone appreciates your effort.
      </p>
    </div>
    <style>
      .container {
        display: block;
        padding-bottom: 1rem;
      }
    </style>
  </body>
</html>