From: Dodji Seketeli <dodji@redhat.com>
To: libabigail@sourceware.org
Cc: dodji@redhat.com
Subject: [PATCH, applied] doc/manuals/libabigail-concepts.rst: Fix typo
Date: Thu, 05 Oct 2023 17:21:58 +0200 [thread overview]
Message-ID: <87fs2pf621.fsf@redhat.com> (raw)
Hello,
* doc/manuals/libabigail-concepts.rst: Fix a typo in the doc for
the "end" named boundary.
Signed-off-by: Dodji Seketeli <dodji@redhat.com>
Applied to master.
---
doc/manuals/libabigail-concepts.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/manuals/libabigail-concepts.rst b/doc/manuals/libabigail-concepts.rst
index f8b5f105..f64f5229 100644
--- a/doc/manuals/libabigail-concepts.rst
+++ b/doc/manuals/libabigail-concepts.rst
@@ -471,8 +471,8 @@ names start with the string "private_data_member".
- data member offset selector expressions, such as:
- - the keyword ``end`` which is a named constant which value
- equals the offset of the end of the of the structure or
+ - the keyword ``end`` which is a named constant which
+ value equals the offset of the end of the structure or
class.
- the function call expression
--
2.39.3
--
Dodji
reply other threads:[~2023-10-05 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87fs2pf621.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=libabigail@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).