public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] manual: Fix typo
Date: Mon,  5 Oct 2020 16:35:30 +0000 (GMT)	[thread overview]
Message-ID: <20201005163530.9F49C383E82D@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5bb2e5300b9b7cf1b8b7f2cbcbfca4d4a529082d

commit 5bb2e5300b9b7cf1b8b7f2cbcbfca4d4a529082d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Oct 5 17:29:38 2020 +0100

    manual: Fix typo

Diff:
---
 manual/threads.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manual/threads.texi b/manual/threads.texi
index 4ab0622443..5bcfe32d6a 100644
--- a/manual/threads.texi
+++ b/manual/threads.texi
@@ -896,7 +896,7 @@ Model Aware Atomic Operations, gcc, Using the GNU Compiler Collection
 
 @smallexample
 if (__libc_single_threaded)
-  ++refeference_count;
+  ++reference_count;
 else
   __atomic_fetch_add (&reference_count, 1, __ATOMIC_ACQ_REL);
 @end smallexample


             reply	other threads:[~2020-10-05 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 16:35 Jonathan Wakely [this message]
2023-01-18 18:28 Florian Weimer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201005163530.9F49C383E82D@sourceware.org \
    --to=redi@sourceware.org \
    --cc=glibc-cvs@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).