From ee05db82189d75a1fc71b58636d6bcfc53d74a2c Mon Sep 17 00:00:00 2001 From: gutteridge Date: Wed, 20 Mar 2019 03:13:39 +0000 Subject: [PATCH] pax: fix typos in comments in file_subs.c & tar.c Stamp out "greengrocers' apostrophes" in various places (arguably there are still more present, but style guides vary on that, and my energies spent corralling wayward punctuation marks could be spent elsewhere). --- bin/pax/file_subs.c | 8 ++++---- bin/pax/tar.c | 16 ++++++++-------- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/bin/pax/file_subs.c b/bin/pax/file_subs.c index cd421d0325b9..4adef153d194 100644 --- a/bin/pax/file_subs.c +++ b/bin/pax/file_subs.c @@ -1,4 +1,4 @@ -/* $NetBSD: file_subs.c,v 1.63 2013/07/29 17:46:36 christos Exp $ */ +/* $NetBSD: file_subs.c,v 1.64 2019/03/20 03:13:39 gutteridge Exp $ */ /*- * Copyright (c) 1992 Keith Muller. @@ -42,7 +42,7 @@ #if 0 static char sccsid[] = "@(#)file_subs.c 8.1 (Berkeley) 5/31/93"; #else -__RCSID("$NetBSD: file_subs.c,v 1.63 2013/07/29 17:46:36 christos Exp $"); +__RCSID("$NetBSD: file_subs.c,v 1.64 2019/03/20 03:13:39 gutteridge Exp $"); #endif #endif /* not lint */ @@ -895,7 +895,7 @@ set_chflags(char *fnm, u_int32_t flags) * actual storage is quite small (the files are sparse). The problem is * the holes read as all zeros so are probably stored on the archive that * way (there is no way to determine if the file block is really a hole, - * we only know that a file block of all zero's can be a hole). + * we only know that a file block of all zeros can be a hole). * At this writing, no major archive format knows how to archive files * with holes. However, on extraction (or during copy, -rw) we have to * deal with these files. Without detecting the holes, the files can @@ -968,7 +968,7 @@ file_write(int fd, char *str, int cnt, int *rem, int *isempt, int sz, if (*isempt) { /* * have not written to this block yet, so we keep - * looking for zero's + * looking for zeros */ pt = st; end = st + wcnt; diff --git a/bin/pax/tar.c b/bin/pax/tar.c index ded2ad47ad2a..513846f4ef24 100644 --- a/bin/pax/tar.c +++ b/bin/pax/tar.c @@ -1,4 +1,4 @@ -/* $NetBSD: tar.c,v 1.74 2018/11/30 00:53:11 christos Exp $ */ +/* $NetBSD: tar.c,v 1.75 2019/03/20 03:13:39 gutteridge Exp $ */ /*- * Copyright (c) 1992 Keith Muller. @@ -42,7 +42,7 @@ #if 0 static char sccsid[] = "@(#)tar.c 8.2 (Berkeley) 4/18/94"; #else -__RCSID("$NetBSD: tar.c,v 1.74 2018/11/30 00:53:11 christos Exp $"); +__RCSID("$NetBSD: tar.c,v 1.75 2019/03/20 03:13:39 gutteridge Exp $"); #endif #endif /* not lint */ @@ -351,7 +351,7 @@ tar_chksm(char *blk, int len) * checksum field as the sum of 8 blanks (which is pre-computed as * BLNKSUM). * ASSUMED: len is greater than CHK_OFFSET. (len is where our 0 padding - * starts, no point in summing zero's) + * starts, no point in summing zeros) */ pt += CHK_LEN; stop = blk + len; @@ -368,7 +368,7 @@ tar_chksm(char *blk, int len) * tar_id() * determine if a block given to us is a valid tar header (and not a USTAR * header). We have to be on the lookout for those pesky blocks of all - * zero's. + * zeros. * Return: * 0 if a tar header, -1 otherwise */ @@ -386,7 +386,7 @@ tar_id(char *blk, int size) uhd = (HD_USTAR *)blk; /* - * check for block of zero's first, a simple and fast test, then make + * check for block of zeros first, a simple and fast test, then make * sure this is not a ustar header by looking for the ustar magic * cookie. We should use TMAGLEN, but some USTAR archive programs are * wrong and create archives missing the \0. Last we check the @@ -769,7 +769,7 @@ ustar_stwr(void) /* * ustar_id() * determine if a block given to us is a valid ustar header. We have to - * be on the lookout for those pesky blocks of all zero's + * be on the lookout for those pesky blocks of all zeros * Return: * 0 if a ustar header, -1 otherwise */ @@ -784,7 +784,7 @@ ustar_id(char *blk, int size) hd = (HD_USTAR *)blk; /* - * check for block of zero's first, a simple and fast test then check + * check for block of zeros first, a simple and fast test then check * ustar magic cookie. We should use TMAGLEN, but some USTAR archive * programs are fouled up and create archives missing the \0. Last we * check the checksum. If ok we have to assume it is a valid header. @@ -1379,7 +1379,7 @@ tar_gnutar_exclude_one(const char *line, size_t len) } /* - * deal with GNU tar -X/--exclude-from & --exclude switchs. basically, + * deal with GNU tar -X/--exclude-from & --exclude switches. basically, * we go through each line of the file, building a string from the "glob" * lines in the file into RE lines, of the form `/^RE$//', which we pass * to rep_add(), which will add a empty replacement (exclusion), for the