public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Simon Marchi <simark@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: remove trailing spaces in README
Date: Wed, 28 Sep 2022 19:04:23 +0000 (GMT)	[thread overview]
Message-ID: <20220928190423.BE56F385740A@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e875475e19d13aa4283571f399848eab64f96ae0

commit e875475e19d13aa4283571f399848eab64f96ae0
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Wed Sep 28 09:58:51 2022 -0400

    gdb: remove trailing spaces in README
    
    Change-Id: Ic7f8e415acd1bff6194cf08ed646bff45571f165

Diff:
---
 gdb/README | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gdb/README b/gdb/README
index bd5a88f348c..406df046053 100644
--- a/gdb/README
+++ b/gdb/README
@@ -39,7 +39,7 @@ You can build GDB right in the source directory:
 
 However, we recommend that an empty directory be used instead.
 This way you do not clutter your source tree with binary files
-and will be able to create different builds with different 
+and will be able to create different builds with different
 configuration options.
 
 You can build GDB in any empty build directory:
@@ -141,7 +141,7 @@ use depends on your system; `lpr -d' is common; another (for PostScript
 devices) is `dvips'.  The DVI print command may require a file name
 without any extension or a `.dvi' extension.
 
-   TeX also requires a macro definitions file called `texinfo.tex'. 
+   TeX also requires a macro definitions file called `texinfo.tex'.
 This file tells TeX how to typeset a document written in Texinfo
 format.  On its own, TeX cannot read, much less typeset a Texinfo file.
  `texinfo.tex' is distributed with GDB and is located in the
@@ -318,7 +318,7 @@ three pieces of information in the following pattern:
 `sparc-sun-sunos4'.
 
    The `configure' script accompanying GDB does not provide any query
-facility to list all supported host and target names or aliases. 
+facility to list all supported host and target names or aliases.
 `configure' calls the Bourne shell script `config.sub' to map
 abbreviations to full names; you can read the script, if you wish, or
 you can use it to test your guesses on abbreviations--for example:
@@ -550,7 +550,7 @@ more obscure GDB `configure' options are not listed here.
      FILE should be an absolute file name.  If FILE is in a directory
      under the configured prefix, and GDB is moved to another location
      after being built, the location of the system-wide init file will
-     be adjusted accordingly. 
+     be adjusted accordingly.
 
 `--with-system-gdbinit-dir=DIR'
      Configure GDB to automatically load system-wide init files from

                 reply	other threads:[~2022-09-28 19:04 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=20220928190423.BE56F385740A@sourceware.org \
    --to=simark@sourceware.org \
    --cc=gdb-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).