From owner-freebsd-doc@FreeBSD.ORG Sat Apr 12 09:00:31 2003 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99FD337B401 for ; Sat, 12 Apr 2003 09:00:31 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84A1343FE3 for ; Sat, 12 Apr 2003 09:00:30 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h3CG0UUp086866 for ; Sat, 12 Apr 2003 09:00:30 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h3CG0Ubk086865; Sat, 12 Apr 2003 09:00:30 -0700 (PDT) Resent-Date: Sat, 12 Apr 2003 09:00:30 -0700 (PDT) Resent-Message-Id: <200304121600.h3CG0Ubk086865@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Dominic Marks Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FEAF37B401; Sat, 12 Apr 2003 08:59:21 -0700 (PDT) Received: from cus.org.uk (host213-106-240-81.no-dns-yet.ntli.net [213.106.240.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95D6543FAF; Sat, 12 Apr 2003 08:59:20 -0700 (PDT) (envelope-from dom@cus.org.uk) Received: from cus.org.uk (localhost.cus.org.uk [127.0.0.1]) by cus.org.uk (8.12.6/8.11.3) with ESMTP id h3CFxJLX081600; Sat, 12 Apr 2003 16:59:19 +0100 (BST) (envelope-from dom@cus.org.uk) Received: (from dom@localhost) by cus.org.uk (8.12.6/8.12.6/Submit) id h3CFxIDO081599; Sat, 12 Apr 2003 16:59:18 +0100 (BST) Message-Id: <200304121559.h3CFxIDO081599@cus.org.uk> Date: Sat, 12 Apr 2003 16:59:18 +0100 (BST) From: Dominic Marks To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 cc: blackend@FreeBSD.org Subject: docs/50871: Updating of Majordomo reference in Handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dominic Marks List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 16:00:32 -0000 >Number: 50871 >Category: docs >Synopsis: Updating of Majordomo reference in Handbook >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 12 09:00:29 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Dominic Marks >Release: FreeBSD 4.7-RELEASE-p3 i386 >Organization: UMIST >Environment: System: FreeBSD moo.cus.org.uk 4.7-RELEASE-p3 FreeBSD 4.7-RELEASE-p3 #3: Mon Jan 20 23:49:12 GMT 2003 root@moo.cus.org.uk:/usr/obj/usr/src/sys/BAA i386 >Description: The Cutting Edge section of the Handbook contains advice about subscribing to mailing lists, it was majordomo centric and since majordomo has gone now, out of date. I've converted this to reflect the current reality of mailman. I've tried to stay within the example set by the eresources section. There is another small patch after the main one which corrects a typo I found in the eresources section while I was creating this patch, goto -> go to. >How-To-Repeat: Read the Cutting Edge section of the Handbook. >Fix: Thanks, Index: chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v retrieving revision 1.183 diff -u -r1.183 chapter.sgml --- chapter.sgml 2003/04/11 01:11:38 1.183 +++ chapter.sgml 2003/04/12 15:53:09 @@ -191,33 +191,25 @@ - Join the &a.current; and the &a.cvsall;. This is not - just a good idea, it is essential. If - you are not on the &a.current;, - you will not see the comments that people are - making about the current state of the system and thus will - probably end up stumbling over a lot of problems that others - have already found and solved. Even more importantly, you - will miss out on important bulletins which may be critical - to your system's continued health. + Join the &a.current.name; and the &a.cvsall.name; + lists. This is not just a good idea, it is + essential. If you are not on the + &a.current.name; list, you will + not see the comments that people are making about the + current state of the system and thus will probably end up + stumbling over a lot of problems that others have already + found and solved. Even more importantly, you will miss + out on important bulletins which may be critical to your + system's continued health. - The &a.cvsall; will allow you to see the + The &a.cvsall.name; list will allow you to see the commit log entry for each change as it is made along with any pertinent information on possible side-effects. - To join these lists, send mail to &a.majordomo; and - specify the following in the body of your message: - - subscribe freebsd-current -subscribe cvs-all - - Majordomo - - - Optionally, you can also say help - and Majordomo will send you full help on how to subscribe - and unsubscribe to the various other mailing lists we - support. + To join these lists, or one of the others available + go to &a.mailman.lists.link; and click on the list that + you wish to subscribe to. Instructions on the rest of the + procedure are available there. @@ -404,32 +396,23 @@ - Join the &a.stable;. This will keep you informed of - build-dependencies that may appear in &os.stable; - or any other issues requiring - special attention. Developers will also make announcements - in this mailing list when they are contemplating some - controversial fix or update, giving the users a chance to - respond if they have any issues to raise concerning the - proposed change. + Join the &a.stable.name; list. This will keep you + informed of build-dependencies that may appear in + &os.stable; or any other issues requiring special + attention. Developers will also make announcements in + this mailing list when they are contemplating some + controversial fix or update, giving the users a chance + to respond if they have any issues to raise concerning + the proposed change. - The &a.cvsall; will allow you to see the + The &a.cvsall.name; list will allow you to see the commit log entry for each change as it is made along with any pertinent information on possible side-effects. - - To join these lists, send mail to &a.majordomo; and - specify the following in the body of your message: - - subscribe freebsd-stable -subscribe cvs-all - - Majordomo - - Optionally, you can also say help - and Majordomo will send you full help on how to subscribe - and unsubscribe to the various other mailing lists we - support. + To join these lists or one of the others available + go to &a.mailman.lists.link; and click on the list that + you wish to subscribe to. Instructions on the rest of + the procedure are available there. Index: chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v retrieving revision 1.118 diff -u -r1.118 chapter.sgml --- chapter.sgml 2003/04/11 01:11:38 1.118 +++ chapter.sgml 2003/04/12 15:38:14 @@ -537,7 +537,7 @@ How to Subscribe To subscribe to a list, click on the list name above or - goto &a.mailman.lists.link; + go to &a.mailman.lists.link; and click on the list that you're interested in. The list page should contain all of the necessary subscription instructions. >Release-Note: >Audit-Trail: >Unformatted: