[src/trunk]: src/sys/arch/alpha Fix typo.

[wiz <wiz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/84532ed5e166
branches:  trunk
changeset: 521026:84532ed5e166
user:      wiz <wiz%NetBSD.org@localhost>
date:      Tue Jan 22 00:04:29 2002 +0000

description:
Fix typo.

diffstat:

 sys/arch/alpha/STYLE |  10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diffs (36 lines):

diff -r a7a19b5032ab -r 84532ed5e166 sys/arch/alpha/STYLE
--- a/sys/arch/alpha/STYLE      Mon Jan 21 23:54:45 2002 +0000
+++ b/sys/arch/alpha/STYLE      Tue Jan 22 00:04:29 2002 +0000
@@ -1,4 +1,4 @@
-$NetBSD: STYLE,v 1.5 2001/07/22 13:34:02 wiz Exp $
+$NetBSD: STYLE,v 1.6 2002/01/22 00:04:29 wiz Exp $
 
 Style guide for NetBSD/alpha kernel files.
 
@@ -35,10 +35,10 @@
 
 RCS IDS
 
-(1) NetBSD RCS ID tags ($NetBSD: STYLE,v 1.5 2001/07/22 13:34:02 wiz Exp $ tags) in C sources and headers should
+(1) NetBSD RCS ID tags ($NetBSD: STYLE,v 1.6 2002/01/22 00:04:29 wiz Exp $ tags) in C sources and headers should
 appear at the top of the file in a single-line comment of the form
 
-/*<space>$NetBSD: STYLE,v 1.5 2001/07/22 13:34:02 wiz Exp $<space>*/
+/*<space>$NetBSD: STYLE,v 1.6 2002/01/22 00:04:29 wiz Exp $<space>*/
 
 which differs from the normal NetBSD style, in that it uses spaces
 rather than tabs to separate the tag from the comment start and end
@@ -47,11 +47,11 @@
 (2) All C and assembler sources should include an RCS ID tag which can
 be compiled into the binary, with a line like:
 
-__KERNEL_RCSID(0, "$NetBSD: STYLE,v 1.5 2001/07/22 13:34:02 wiz Exp $");
+__KERNEL_RCSID(0, "$NetBSD: STYLE,v 1.6 2002/01/22 00:04:29 wiz Exp $");
 
 after the inclusion of cdefs.h.  Source files which include other source
 files should change the number '0' to a different number, so that it
-doesn't conflict with the RCS ID definitios in included sources.
+doesn't conflict with the RCS ID definitions in included sources.
 Generation of these RCS IDs is disabled if the kernel option
 NO_KERNEL_RCSIDS is defined.  (In some cases, picking the number to use
 may not be so straightforward, but the rule above usually works.)