Fix for "and and" and "the the" typos in the README file.

(weijg.fnst@cn.fujitsu.com)
This commit is contained in:
Dave Anderson 2015-04-27 12:05:36 -04:00
parent 117284469a
commit 1c10f98a56
2 changed files with 4 additions and 4 deletions

4
README
View File

@ -79,7 +79,7 @@
$ make
The initial build will take several minutes because the embedded gdb module
must be configured and and built. Alternatively, the crash source RPM file
must be configured and built. Alternatively, the crash source RPM file
may be installed and built, and the resultant crash binary RPM file installed.
The crash binary can only be used on systems of the same architecture as
@ -344,7 +344,7 @@
Alternatively, you can create shared object library files consisting of
crash command extensions, that can be dynamically linked into the crash
executable during runtime or during initialization. This will allow the
executable during runtime or during initialization. This will allow
the same shared object to be used with subsequent crash releases without
having to re-merge the command's code into each new set of crash sources.
The dynamically linked-in commands will automatically show up in the crash

4
help.c
View File

@ -8047,7 +8047,7 @@ README_ENTER_DIRECTORY,
" $ make",
"",
" The initial build will take several minutes because the embedded gdb module",
" must be configured and and built. Alternatively, the crash source RPM file",
" must be configured and built. Alternatively, the crash source RPM file",
" may be installed and built, and the resultant crash binary RPM file installed.",
"",
" The crash binary can only be used on systems of the same architecture as",
@ -8272,7 +8272,7 @@ README_GNU_GDB_VERSION,
"",
" Alternatively, you can create shared object library files consisting of",
" crash command extensions, that can be dynamically linked into the crash",
" executable during runtime or during initialization. This will allow the",
" executable during runtime or during initialization. This will allow",
" the same shared object to be used with subsequent crash releases without",
" having to re-merge the command's code into each new set of crash sources.",
" The dynamically linked-in commands will automatically show up in the crash",