GNU bug report logs - #72606
[PATCH] Fix typos

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#72606: closed ([PATCH] Fix typos)
Date: Wed, 14 Aug 2024 14:36:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 14 Aug 2024 17:33:54 +0300
with message-id <1068cf70-14e4-46c7-9725-ec01e0169591 <at> gmail.com>
and subject line Re: bug#72606: [PATCH] Fix typos
has caused the debbugs.gnu.org bug report #72606,
regarding [PATCH] Fix typos
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
72606: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=72606
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Tobias Stoeckmann <tobias <at> stoeckmann.org>
To: bug-libtool <at> gnu.org
Subject: [PATCH] Fix typos
Date: Tue, 13 Aug 2024 21:56:58 +0200

Typos found with codespell.
---
 doc/libtool.texi | 2 +-
 doc/notes.texi   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/libtool.texi b/doc/libtool.texi
index b212b24c..04ab34f1 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -5594,7 +5594,7 @@ running the @command{libtool} test cases.
 Tests @command{libtool}'s versioning system.  Tests begin with verifying the
 behaviour of @command{libtool} versioning flags @option{-version-info} and
 @option{-version-number}.  Next, this tests installing a library, then updating
-the library with a new revision, a compatible update, and an incompatabile
+the library with a new revision, a compatible update, and an incompatible
 update.  In each case, the tests verify that the original library will link and
 install as expected.

diff --git a/doc/notes.texi b/doc/notes.texi
index 606c957b..7b6ade8d 100644
--- a/doc/notes.texi
+++ b/doc/notes.texi
@@ -27,7 +27,7 @@ will generate the instantiations.  For Portland pgCC version5, use
 @code{CXX='pgCC --one_instantiation_per_object'} and avoid parallel @command{make}.

 @item
-For C++ code, it may be neccesary to specify a library if it is a dependency
+For C++ code, it may be necessary to specify a library if it is a dependency
 of a link/compile flag. For example in GNU G++, if you want to use
 @code{-fsanitize=address} you need to specify the @code{-lasan} library,
 like so: @code{g++ -o libx.la -fsanitize=address -lasan -rpath [...]}.
--
2.46.0

[Message part 3 (message/rfc822, inline)]

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 72606-done <at> debbugs.gnu.org
Cc: Tobias Stoeckmann <tobias <at> stoeckmann.org>
Subject: Re: bug#72606: [PATCH] Fix typos
Date: Wed, 14 Aug 2024 17:33:54 +0300

[Message part 4 (text/plain, inline)]

Hi Tobias,

On 13/08/2024 22:56, Tobias Stoeckmann wrote:
> Typos found with codespell.
> ---
>   doc/libtool.texi | 2 +-
>   doc/notes.texi   | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/libtool.texi b/doc/libtool.texi
> index b212b24c..04ab34f1 100644
> --- a/doc/libtool.texi
> +++ b/doc/libtool.texi
> @@ -5594,7 +5594,7 @@ running the @command{libtool} test cases.
>   Tests @command{libtool}'s versioning system.  Tests begin with verifying the
>   behaviour of @command{libtool} versioning flags @option{-version-info} and
>   @option{-version-number}.  Next, this tests installing a library, then updating
> -the library with a new revision, a compatible update, and an incompatabile
> +the library with a new revision, a compatible update, and an incompatible
>   update.  In each case, the tests verify that the original library will link and
>   install as expected.
> 
> diff --git a/doc/notes.texi b/doc/notes.texi
> index 606c957b..7b6ade8d 100644
> --- a/doc/notes.texi
> +++ b/doc/notes.texi
> @@ -27,7 +27,7 @@ will generate the instantiations.  For Portland pgCC version5, use
>   @code{CXX='pgCC --one_instantiation_per_object'} and avoid parallel @command{make}.
> 
>   @item
> -For C++ code, it may be neccesary to specify a library if it is a dependency
> +For C++ code, it may be necessary to specify a library if it is a dependency
>   of a link/compile flag. For example in GNU G++, if you want to use
>   @code{-fsanitize=address} you need to specify the @code{-lasan} library,
>   like so: @code{g++ -o libx.la -fsanitize=address -lasan -rpath [...]}.
> --
> 2.46.0
> 

Thank you for your patch. It has been applied to development, which will
be merged into master before the next release:
https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=bb5694666b3fdbf680cdffbaf7085fb0ad8dea86

-- 
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354

[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.