Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
home:Ledest:erlang:23
erlang
1518-Correct-typos.patch
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File 1518-Correct-typos.patch of Package erlang
From d5a4491c0756d9772cdfe828e9a82aefd9e2b2f9 Mon Sep 17 00:00:00 2001 From: Cesar Guzman <ironjanowar@gmail.com> Date: Sat, 25 May 2024 11:54:09 +0200 Subject: [PATCH] Correct typos PR change requests PR comment PR comment --- HOWTO/BOOTSTRAP.md | 2 +- erts/emulator/beam/erl_db_util.c | 2 +- lib/compiler/test/guard_SUITE.erl | 2 +- lib/erl_interface/src/README.internal | 2 +- lib/reltool/src/reltool.erl | 2 +- lib/ssh/src/ssh_transport.erl | 2 +- lib/stdlib/src/gen_event.erl | 4 ++-- lib/stdlib/src/gen_server.erl | 4 ++-- lib/stdlib/src/gen_statem.erl | 4 ++-- 9 files changed, 12 insertions(+), 12 deletions(-) diff --git a/HOWTO/BOOTSTRAP.md b/HOWTO/BOOTSTRAP.md index a81bdc1f37..e719f93c73 100644 --- a/HOWTO/BOOTSTRAP.md +++ b/HOWTO/BOOTSTRAP.md @@ -14,7 +14,7 @@ Primary bootstrap The two types of version controlled code are fundamentally different. The primary bootstrap is code compiled from source files in -the lib/{kernel,stdlib,compiler} (They are checked in in the version control system +the lib/{kernel,stdlib,compiler} (They are checked in the version control system to make it possible to build directly from the code base tree without the need for an earlier version of the compiler. When a new version of OTP is released, these files are updated manually (or rather, by using diff --git a/erts/emulator/beam/erl_db_util.c b/erts/emulator/beam/erl_db_util.c index 2029ed67ab..567e16a93b 100644 --- a/erts/emulator/beam/erl_db_util.c +++ b/erts/emulator/beam/erl_db_util.c @@ -3980,7 +3980,7 @@ static void vadd_dmc_err(DMCErrInfo *err_info, va_start(args, str); - /* Linked in in reverse order, to ease the formatting */ + /* Linked in reverse order, to ease the formatting */ e = erts_alloc(ERTS_ALC_T_DB_DMC_ERROR, sizeof(DMCError)); erts_vsnprintf(e->error_string, DMC_ERR_STR_LEN, str, args); e->variable = variable; diff --git a/lib/compiler/test/guard_SUITE.erl b/lib/compiler/test/guard_SUITE.erl index 95ca6d15f7..291992d26c 100644 --- a/lib/compiler/test/guard_SUITE.erl +++ b/lib/compiler/test/guard_SUITE.erl @@ -2775,7 +2775,7 @@ welcome({perfect, Profit}) -> maps() -> ok = evidence(#{0 => 42}). -%% Cover handling of put_map in in split_block_label_used/2. +%% Cover handling of put_map in split_block_label_used/2. evidence(#{0 := Charge}) when 0; #{[] => Charge} == #{[] => 42} -> ok. diff --git a/lib/erl_interface/src/README.internal b/lib/erl_interface/src/README.internal index f0e27ec358..7e9f73d803 100644 --- a/lib/erl_interface/src/README.internal +++ b/lib/erl_interface/src/README.internal @@ -242,7 +242,7 @@ located in the file "ei_x_encode.c". So if any "long long" ei_x function is used we have an unessesary dependency on "ei_encode_longlong.o" and then need to link with GNU ld on with the user code or explicitly link with "libgcc.a". The situation can be -visible in in plain R9C using +visible in plain R9C using % nm -A erl_interface-3.4/lib/libei.a | \ grep 'longlong' | fgrep -v 'longlong.o' diff --git a/lib/reltool/doc/src/reltool.xml b/lib/reltool/doc/src/reltool.xml index 0a1067cfe6..afadac6ba8 100644 --- a/lib/reltool/doc/src/reltool.xml +++ b/lib/reltool/doc/src/reltool.xml @@ -193,7 +193,7 @@ <p>The creation of the specification for a target system is performed in two steps. In the first step a complete specification is generated. It will likely contain much more - files than you are interested in in your customized target + files than you are interested in your customized target system. In the second step the specification will be filtered according to your filters. There you have the ability to specify filters per application as well as system wide @@ -557,7 +557,7 @@ target_spec() = [target_spec()] the specification for a target system is performed in two steps. In the first step a complete specification will be generated. It will likely contain much more files than you are - interested in in your target system. In the second step the + interested in your target system. In the second step the specification will be filtered according to your filters. There you have the ability to specify filters per application as well as system wide filters. You can also select a <c>profile</c> for diff --git a/lib/ssh/src/ssh_transport.erl b/lib/ssh/src/ssh_transport.erl index d6e5f2955b..717652c8d1 100644 --- a/lib/ssh/src/ssh_transport.erl +++ b/lib/ssh/src/ssh_transport.erl @@ -1587,7 +1587,7 @@ do_verify(PlainText, HashAlg, Sig, {#'ECPoint'{},_} = Key, _) when HashAlg =/= u verify(PlainText, HashAlg, Sig, #'RSAPublicKey'{}=Key, #ssh{role = server, c_version = "SSH-2.0-OpenSSH_7."++_}) when HashAlg == sha256; HashAlg == sha512 -> - %% Public key signing bug in in OpenSSH >= 7.2 + %% Public key signing bug in OpenSSH >= 7.2 public_key:verify(PlainText, HashAlg, Sig, Key) orelse public_key:verify(PlainText, sha, Sig, Key); -- 2.35.3
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor