回复git@vger.kernel.org的注意事项

比如回复这封邮件 https://public-inbox.org/git/db2dcf54-8b1c-39b1-579c-425ef158c6a1@kdbg.org/

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75618ca1-748d-0761-9108-c7deac63cb53@iee.org \
    --to=philipoakley@iee.org \
    --cc=Chuck.LU@edenred.com \
    --cc=chuck.lu@qq.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Avoid top-posting and favor interleaved quoting 使用interleaved引用来回复

top-posting

https://en.wikipedia.org/wiki/Posting_style#Top-posting

In top-posting style, the original message is included verbatim, with the reply above it. It is sometimes referred to by the acronym TOFU ("text over, fullquote under"). It has also been colloquially referred to as Jeopardy! reply style: as in the game show's signature clue/response format, the answers precede the question.

Example:

No problem.  6pm it is then.
Jim

-------- Original Message --------
From: Danny <danny@example.com>
Sent: Tuesday, October 16, 2007 10:01 AM
To: Jim <jim@example.com>
Subject: RE: Job

Whoa!  Hold on.  I have a job scheduled at 5:30 which mails out
a report to key tech staff.  Could you please push it back an hour?
Danny

-------- Original Message --------
From: Jim <jim@example.com>
Sent: Tuesday, October 16, 2007 9:40 AM
To: Danny <danny@example.com>
Subject: Job

I'm going to suspend the mail service for approx. thirty
minutes tonight, starting at 5pm, to install some updates
and important fixes.
Jim

Top-posting preserves an apparently unmodified transcript of a branch in the conversation. Often all replies line up in a single branch of a conversation. The top of the text shows the latest replies. This appears to be advantageous for business correspondence, where an e-mail thread can dupe others into believing it is an "official" record.^{[citation needed]}

By contrast, excessive indentation of interleaved and bottom posting may turn difficult to interpret. If the participants have different stature such as manager vs. employee or consultant vs. client, one person's cutting apart another person's words without the full context may look impolite or cause misunderstanding.

In the earlier days of Usenet informal discussions where everyone was an equal encouraged bottom-posting. Until the mid-1990s, posts in a net.newcomers newsgroup insisted on interleaving replies. Usenet comp.lang hierarchy, especially comp.lang.c and comp.lang.c++ insisted on the same as of the 2010s. The alt hierarchy tolerated top-posting. Newer online participants, especially those with limited experience of Usenet, tend to be less sensitive to arguments about posting style.

Top-posting can be problematic on mailing lists with ongoing discussions which eventually require someone to act on the top-posted material. For example, top-posting "Those changes look ok to me, go ahead and make them" can be very inconvenient for the person who needs to make the changes if he or she has to read through a long email trail to know which changes the top-poster is referring to. Inter-leaving the text directly below the text describing the changes is much more convenient in these cases.

Users of mobile devices, like smartphones, are encouraged to use top-posting because the devices may only download the beginning of a message for viewing. The rest of the message is only retrieved when needed, which takes additional download time. Putting the relevant content at the beginning of the message requires less bandwidth, less time, and less scrolling for the user.^[4][5][6]

Top-posting is a natural consequence of the behavior of the "reply" function in many current e-mail readers, such as Microsoft Outlook, Gmail, and others. By default, these programs insert into the reply message a copy of the original message (without headers and often without any extra indentation or quotation markers), and position the editing cursor above it. Moreover, a bug present on most flavours of Microsoft Outlook caused the quotation markers to be lost when replying in plain text to a message that was originally sent in HTML/RTF.^{[citation needed]} For these and possibly other reasons, many users seem to accept top-posting as the "standard" reply style.

Partially because of Microsoft's influence, top-posting is very common on mailing lists and in personal e-mail.^{[7][8][9][10]}

Top-posting has always been the standard format for forwarding a message to a third party, in which case the comments at the top (if any) are a "cover note" for the recipient.

Interleaved style

https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

In the interleaved reply style (also called "inline reply", "interlined reply", "point-by-point rebuttal", or, sometimes, "bottom posting"), the original message is broken into two or more sections, each followed by a specific reply or comment. A reply in inline style may also include some top-posted or bottom-posted comments that apply to the whole reply message, rather than to a specific point. For example:

I have been following the discussion about the new product line. Here are my thoughts.

Joe wrote:

> Will our prices be competitive?

That may not be a problem for now, we still have a quality edge.

> We do not have enough trained people on the West Coast. We have many
> new employees but they do not know our products yet.

We can bring them here for a crash training course.

Mary wrote:

> We still do not have a clear marketing plan.

Peter, would you take charge of that? Let me know if you need help.

On the whole, I am quite optimistic.  It looks like we will be shipping
the basic system before the end of this quarter.
Nancy

The interleaved reply style can also be combined with top-posting: selected points are quoted and replied to, as above, and then a full copy of the original message is appended.

> Can you present your report an hour later?

Yes I can. The summary will be sent no later than 5pm.
Jim

At 10.01am Wednesday, Danny wrote:
>> 2.00pm: Present report
> Jim, I have a meeting at that time. Can you present your report an hour later?
>
>> 4.30pm: Send out summary of feedback
> Also if you do the above, this may need to happen later too.
> Danny
>
> At 9.40am Wednesday, Jim wrote:
>> My schedule for today will be:
>> 10.00am: Gather data for report
>> 2.00pm: Present report to team
>> 4.30pm: Send out summary of feedback
>> Jim

Interleaving was the predominant reply style in the Usenet discussion lists, years before the existence of the WWW and the spread of e-mail and the Internet outside the academic community.^[3]

Interleaving was also common originally in e-mail, because many internet users had been exposed to Usenet newsgroups and other Internet forums, where it is still used.^{[citation needed]} The style became less common for email after the opening of the internet to commercial and non-academic personal use.^{[citation needed]} One possible reason is the large number of casual e-mail users that entered the scene at that time.^{[citation needed]} Another possible reason is the inadequate support provided by the reply function of some webmail readers, which either do not automatically insert a copy of the original message into the reply, or do so without any quoting prefix level indicators.^{[citation needed]} Finally, most forums, wiki discussion pages, and blogs (such as Slashdot) essentially impose the bottom-post format, by displaying all recent messages in chronological order.^{[citation needed]}. Interleaving continues to be used on technical mailing lists where clarity within complex threads is important.^{[citation needed]}.