From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Update to version 1.20.2
Date: Thu, 23 May 2024 17:59:04 +0100 [thread overview]
Message-ID: <08EB28E1-170E-4C1F-9AF1-7B52F1A20255@ipfire.org> (raw)
In-Reply-To: <20240520133525.3502954-2-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2879 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 20 May 2024, at 14:35, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update from version 1.20 to 1.20.2
> - Update of root filr not required
> - Changelog
> 1.20.2
> A bug has been fixed that made global commands like 'g/x/s/x/x', with the last
> delimiter omitted, print every substituted line twice.
> (Bug introduced in 1.18. Reported by Douglas McIlroy).
> 1.20.1
> New command-line options '+line', '+/RE', and '+?RE' have been implemented to
> set the current line to the line number specified or to the first or last line
> matching the regular expression 'RE'.
> (Suggested by Matthew Polk and John Cowan).
> File names containing control characters 1 to 31 are now rejected unless they
> are allowed with the command-line option '--unsafe-names'.
> File names containing control characters 1 to 31 are now printed using octal
> escape sequences.
> Ed now rejects file names ending with a slash.
> Intervening commands that don't set the modified flag no longer make a second
> 'e' or 'q' command fail with a 'buffer modified' warning.
> Tilde expansion is now performed on file names supplied to commands; if a file
> name starts with '~/', the tilde (~) is expanded to the contents of the
> variable HOME. (Suggested by John Cowan).
> Ed now warns the first time that a command modifies a buffer loaded from a
> read-only file. (Suggested by Dan Jacobson).
> It has been documented that 'e' creates an empty buffer if file does not exist.
> It has been documented that 'f' sets the default filename, whether or not its
> argument names an existing file.
> The description of the exit status has been improved in '--help' and in the
> manual.
> The variable MAKEINFO has been added to configure and Makefile.in.
> It has been documented in INSTALL that when choosing a C standard, the POSIX
> features need to be enabled explicitly:
> ./configure CFLAGS+='--std=c99 -D_POSIX_C_SOURCE=2'
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/ed | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/ed b/lfs/ed
> index 633ec4055..7f5072cf4 100644
> --- a/lfs/ed
> +++ b/lfs/ed
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.20
> +VER = 1.20.2
>
> THISAPP = ed-$(VER)
> DL_FILE = $(THISAPP).tar.lz
> @@ -39,7 +39,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = d212c6d5302627145332ec25b989ca2d4a064ce5c0ea45ad1ad6b780ffd72037ff2144b933c52667c52192d6f5acd5766b5c31d4a2b5cf5993813c43e1523af3
> +$(DL_FILE)_BLAKE2 = 5a9d36dba98488e3cacb3e4c0b9d70003345ca94dbf9a3ebd3181b93567b9ef94df0e72614e99e2c6dde4929933d9333c6dba90fafcea6962e2c1abccb0525af
>
> install : $(TARGET)
>
> --
> 2.44.0
>
next prev parent reply other threads:[~2024-05-23 16:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 13:35 [PATCH] cpio: Update to version 2.15 Adolf Belka
2024-05-20 13:35 ` [PATCH] ed: Update to version 1.20.2 Adolf Belka
2024-05-23 16:59 ` Michael Tremer [this message]
2024-05-20 13:35 ` [PATCH] iana-etc: Update to version 20240502 Adolf Belka
2024-05-23 16:59 ` Michael Tremer
2024-05-20 13:35 ` [PATCH] jq: Update to version 1.7.1 Adolf Belka
2024-05-23 16:59 ` Michael Tremer
2024-05-20 13:35 ` [PATCH] kbd: Update to version 2.6.4 Adolf Belka
2024-05-23 17:00 ` Michael Tremer
2024-05-20 13:35 ` [PATCH] pam: Update to version 1.6.1 Adolf Belka
2024-05-23 16:59 ` Michael Tremer
2024-05-20 13:35 ` [PATCH] screen: Update to version 4.9.1 Adolf Belka
2024-05-23 16:59 ` Michael Tremer
2024-05-23 16:58 ` [PATCH] cpio: Update to version 2.15 Michael Tremer
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=08EB28E1-170E-4C1F-9AF1-7B52F1A20255@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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