From: Jonny Grant <jg@jguk.org>
To: libc-alpha@sourceware.org
Subject: rt: Fix comments in <aliases.h>
Date: Tue, 6 Oct 2020 21:37:25 +0100 [thread overview]
Message-ID: <4252d593-88df-d608-fbe9-fb7611aa5993@jguk.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
Hello
Removed the space in "data base" as it's always written as "database".
ChangeLog:
2020-10-06 Jonny Grant <jg@jguk.org>
* aliases.h: Fix comments.
[-- Attachment #2: aliases.h.patch --]
[-- Type: text/x-patch, Size: 1093 bytes --]
--- aliases.h.orig 2020-10-06 21:33:51.461055723 +0100
+++ aliases.h 2020-10-06 21:34:38.529434711 +0100
@@ -22,10 +22,9 @@
#include <sys/types.h>
-
__BEGIN_DECLS
-/* Structure to represent one entry of the alias data base. */
+/* Structure to represent one entry of the alias database. */
struct aliasent
{
char *alias_name;
@@ -35,16 +34,16 @@
};
-/* Open alias data base files. */
+/* Open alias database files. */
extern void setaliasent (void) __THROW;
-/* Close alias data base files. */
+/* Close alias database files. */
extern void endaliasent (void) __THROW;
-/* Get the next entry from the alias data base. */
+/* Get the next entry from the alias database. */
extern struct aliasent *getaliasent (void) __THROW;
-/* Get the next entry from the alias data base and put it in RESULT_BUF. */
+/* Get the next entry from the alias database and put it in RESULT_BUF. */
extern int getaliasent_r (struct aliasent *__restrict __result_buf,
char *__restrict __buffer, size_t __buflen,
struct aliasent **__restrict __result) __THROW;
next reply other threads:[~2020-10-06 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 20:37 Jonny Grant [this message]
2020-10-19 8:50 ` rt: Fix comments in <aliases.h> Florian Weimer via Libc-alpha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4252d593-88df-d608-fbe9-fb7611aa5993@jguk.org \
--to=jg@jguk.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).