From: Bob Wilson <bwilson@tensilica.com>
To: binutils@sources.redhat.com
Subject: fix ld documentation typo
Date: Mon, 17 May 2004 22:50:00 -0000 [thread overview]
Message-ID: <40A941B0.3050904@tensilica.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
I stumbled across this typo today. Someone must have swapped around some
sections and forgot to update the subsection name. Committed as obvious.
2004-05-17 Bob Wilson <bob.wilson@acm.org>
* ld.texinfo (Output Section Address): Correct subsection name.
[-- Attachment #2: ld.texinfo.diff --]
[-- Type: text/plain, Size: 530 bytes --]
Index: ld.texinfo
===================================================================
RCS file: /cvs/src/src/ld/ld.texinfo,v
retrieving revision 1.113
diff -u -r1.113 ld.texinfo
--- ld.texinfo 7 May 2004 15:17:57 -0000 1.113
+++ ld.texinfo 17 May 2004 22:47:05 -0000
@@ -2834,7 +2834,7 @@
Discarding}.
@node Output Section Address
-@subsection Output Section Description
+@subsection Output Section Address
@cindex address, section
@cindex section address
The @var{address} is an expression for the VMA (the virtual memory
reply other threads:[~2004-05-17 22:50 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=40A941B0.3050904@tensilica.com \
--to=bwilson@tensilica.com \
--cc=binutils@sources.redhat.com \
/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).