Mailing lists

From Linux PARISC Wiki
(Difference between revisions)
Jump to: navigation, search
m
Line 1: Line 1:
'''linux-parisc''' [[[http://www.spinics.net/lists/linux-parisc/ spinics archive]], [[http://dir.gmane.org/gmane.linux.ports.parisc gmane archive]]]
+
The [mailto:linux-parisc@vger.kernel.org linux-parisc@vger.kernel.org] mailing list exists to serve PA-RISC developers and developement
 
+
This mailing list exists to serve PA-RISC developers and developement
+
 
communities closely tied to them. This primarily (but not exclusively)
 
communities closely tied to them. This primarily (but not exclusively)
 
means linux kernel, gcc, binutils, and glibc work.
 
means linux kernel, gcc, binutils, and glibc work.
  
To subscribe, please mail [[mailto:majordomo@vger.kernel.org majordomo@vger.kernel.org]] with the message content '''subscribe linux-parisc'''.
+
Archives for [mailto:linux-parisc@vger.kernel.org linux-parisc] are available at:
 +
* [http://www.spinics.net/lists/linux-parisc/ spinics archive]
 +
* [http://dir.gmane.org/gmane.linux.ports.parisc gmane archive]
  
 +
To subscribe, please mail [mailto:majordomo@vger.kernel.org majordomo@vger.kernel.org] with the message content '''subscribe linux-parisc'''.
  
 
'''Rules:'''
 
'''Rules:'''
  
* Post user space questions to [[mailto:debian-hppa@lists.debian.org debian-hppa]] mailing list.
+
# Post user space questions to [mailto:debian-hppa@lists.debian.org debian-hppa mailing list].
* Use '''reportbug''' to file problem reports for specific applications.
+
# Use '''reportbug''' to file problem reports for specific applications.
* Before posting a kernel problem report or question:
+
# Before posting a kernel problem report or question:
# Review [[this list]] of things to check for the answer.
+
## Review [[this list]] of things to check for the answer.
# Read [[http://www.catb.org/~esr/faqs/smart-questions.html How-To Ask Smart Questions]]
+
## Read [http://www.catb.org/~esr/faqs/smart-questions.html How-To Ask Smart Questions]
# Read [[How to report a parisc-linux kernel problem]]
+
## Read [[How to report a parisc-linux kernel problem]]
# If you want to guess what the problem is, please include a patch.
+
## If you want to guess what the problem is, please include a patch.
* '''Really.''' Read the above stuff at least once. It tells you what we need to know to help and how to communicate that information.
+
 
*  parisc-linux is an '''open list'''. While the list has a spamfilter, we apologize some spam does get through anyway because this list is open.<br> Here is the most basic etiquette for open lists:
+
'''Really.''' Read the above stuff at least once. It tells you what we need to know to help and how to communicate that information.
* '''NEVER''' CC: or cross post to a closed mailing list.
+
* '''NEVER''' answer in private to a mailing-list message.
+
* '''NEVER''' ask if you can ask a question.    (Just ask it once you've done your homework.)
+
  
 
'''Search the old "parisc-linux@parisc-linux.org" mailing lists (before the switch to "linux-parisc@vger.kernel.org")'''  
 
'''Search the old "parisc-linux@parisc-linux.org" mailing lists (before the switch to "linux-parisc@vger.kernel.org")'''  
 
'''parisc-linux-cvs''' [[[archive]]]
 
'''parisc-linux-cvs''' [[[archive]]]
 
'''Note to Microsoft Exchange users:''' Please setup your email client
 
so it '''does not''' send automatic "Out-of-Office" replies to list mail.
 
Instructions for how to do this with Microsoft Outlook are
 
[[http://parisc-linux.org/mailing-lists/outlookooo.html available here]]
 

Revision as of 21:12, 6 November 2013

The linux-parisc@vger.kernel.org mailing list exists to serve PA-RISC developers and developement communities closely tied to them. This primarily (but not exclusively) means linux kernel, gcc, binutils, and glibc work.

Archives for linux-parisc are available at:

To subscribe, please mail majordomo@vger.kernel.org with the message content subscribe linux-parisc.

Rules:

  1. Post user space questions to debian-hppa mailing list.
  2. Use reportbug to file problem reports for specific applications.
  3. Before posting a kernel problem report or question:
    1. Review this list of things to check for the answer.
    2. Read How-To Ask Smart Questions
    3. Read How to report a parisc-linux kernel problem
    4. If you want to guess what the problem is, please include a patch.

Really. Read the above stuff at least once. It tells you what we need to know to help and how to communicate that information.

Search the old "parisc-linux@parisc-linux.org" mailing lists (before the switch to "linux-parisc@vger.kernel.org") parisc-linux-cvs [[[archive]]]

Personal tools