From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1879) id BE56F385740A; Wed, 28 Sep 2022 19:04:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE56F385740A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1664391863; bh=RWtTasnJkXSu2vqVqtb/9jRDqVe56zCQEa67Q0iHCmg=; h=From:To:Subject:Date:From; b=r7eVq7xVKL8+IgEF5exAcKUHkIomPwr8/Y+ucQRe9g4gU0r5dBW47uVYOwb33bGVj NzpGfnjWtIqUA9os0gHTZ7GS+9nT2vx80DpQs1DQ6RPhDihMJVynR2/WNjg7lO7sls A4deAo3Ak/r/hy/VdUu9vvACOamhqtGYb9ndSs4k= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Simon Marchi To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: remove trailing spaces in README X-Act-Checkin: binutils-gdb X-Git-Author: Simon Marchi X-Git-Refname: refs/heads/master X-Git-Oldrev: 98847c1e38b717ceb7d186fe377be53171a9225f X-Git-Newrev: e875475e19d13aa4283571f399848eab64f96ae0 Message-Id: <20220928190423.BE56F385740A@sourceware.org> Date: Wed, 28 Sep 2022 19:04:23 +0000 (GMT) List-Id: https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3De875475e19d1= 3aa4283571f399848eab64f96ae0 commit e875475e19d13aa4283571f399848eab64f96ae0 Author: Simon Marchi Date: Wed Sep 28 09:58:51 2022 -0400 gdb: remove trailing spaces in README =20 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: =20 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=20 +and will be able to create different builds with different configuration options. =20 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. =20 - TeX also requires a macro definitions file called `texinfo.tex'.=20 + 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'. =20 The `configure' script accompanying GDB does not provide any query -facility to list all supported host and target names or aliases.=20 +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 her= e. 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.=20 + be adjusted accordingly. =20 `--with-system-gdbinit-dir=3DDIR' Configure GDB to automatically load system-wide init files from