Changes between Version 42 and Version 43 of RTEMSMailingLists

Timestamp:

11/12/18 19:00:26 (6 years ago)

Author:

a-bhatt

Comment:

minor grammatical errors

RTEMSMailingLists

@@ -14 +14 @@
 * RTEMS Developers ([mailto:devel@rtems.org devel@rtems.org]) is about the development of RTEMS. Send patches here. ([http://lists.rtems.org/mailman/listinfo/devel subscribe]) ([http://lists.rtems.org/mailman/listinfo/devel archives])
 
-* The RTEMS Developers list is about developing RTEMS. It is about the implementation of RTEMS and covers a wide range of technical issues as well as directional issues relating to the way the project develops, maintains and releases RTEMS. This lists covers the maintenance of the tools RTEMS uses, new Board Support Packages, new features, and technical implementation details for third party packages bundled with RTEMS. It is technical. The list also accepts patches to RTEMS. If you have patches please send them to this list. It is the main point of view. Any responses to posts to the Version Control (rtems-vc@rtems.org) or Bugs (rtems-bugs@rtems.org) lists should be posted to this list as those lists are blocked to posting.
+* The RTEMS Developers list is about developing RTEMS. It is about the implementation of RTEMS and covers a wide range of technical issues as well as directional issues relating to the way the project develops, maintains and releases RTEMS. This lists covers the maintenance of the tools RTEMS uses, new Board Support Packages, new features, and technical implementation details for third-party packages bundled with RTEMS. It is technical. The list also accepts patches to RTEMS. If you have patches please send them to this list. It is the main point of view. Any responses to posts to the Version Control (rtems-vc@rtems.org) or Bugs (rtems-bugs@rtems.org) lists should be posted to this list as those lists are blocked to posting.
 
 == Policies ==
@@ -35 +35 @@
 }}}
 
-Such disclaimers are inappropriate for mail sent to public lists. You have knowingly submitted your post to a public list which is sent to hundreds or thousands or users and archived on multiple servers around the world.  You have assumed that your unsolicited request should be honored by people who did not agree to it explicitly.  Worst of all, you expect someone to answer your supposedly confidential request.  Overall, it is quite absurd for the paragraph to even be put on email.  
+Such disclaimers are inappropriate to be sent to public lists. You have knowingly submitted your post to a public list which is sent to hundreds or thousands of users and archived on multiple servers around the world.  You have assumed that your unsolicited request should be honored by people who did not agree to it explicitly.  Worst of all, you expect someone to answer your supposedly confidential request.  Overall, it is quite absurd for the paragraph to even be put on email.  
 
 If your company automatically adds something like this to outgoing mail, and you can't convince them to stop, you might consider using a free web-based e-mail account. Notices like this:
@@ -48 +48 @@
 == Posting from multiple accounts ==
 
-If you like to post to a mailing list from more than one account, but only want to receive email to one account, you can subscribe to the list then send an email to:
+If you like to post to a mailing list from more than one account, but only want to receive e-mails on one account, you can subscribe to the list then send an email to:
 
 users-request@rtems.org with the body `set delivery off`. (Or similarly for devel-request@rtems.org)