public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Cc: Matthias Fischer <matthias.fischer@ipfire.org>
Subject: [PATCH] nano: Update to 9.1
Date: Wed, 24 Jun 2026 12:09:46 +0200	[thread overview]
Message-ID: <20260624100948.3366703-1-matthias.fischer@ipfire.org> (raw)

For details see:
https://www.nano-editor.org/news.php

"2026 June 23 - GNU nano 9.1 "met een hongerig paard aan ons been"

    When searching, the viewport is placed snug left where possible.

    The ability to read and write files in old Mac format was removed
    (that is: files that use a lone carriage return as line ending).

    The ^T toggle between WhereIs and GotoLine has been dropped.

    When --backup is active, in some situations no backup was made,
    or it had a wrong timestamp. Both issues are fixed now.

    When nano is killed or crashes, any .save file is not chmodded
    to the permissions of the base file, nor chowned to its owner.

    M-Ins and M-Del have become rebindable."

Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
---
 lfs/nano | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lfs/nano b/lfs/nano
index 306c9252a..6f0793d16 100644
--- a/lfs/nano
+++ b/lfs/nano
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 9.0
+VER        = 9.1
 
 THISAPP    = nano-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 6df92e9f1b0ba8c2ec3dfdd8b4605a34c08f33c747746d8d3b4145894f0cc64b705c59f2b5aee120050eb32292adf78bf267c568a266c17e2f99e48026d38106
+$(DL_FILE)_BLAKE2 = d762076463b0c683d13cd4c47cc05db573a1890c9ea0629c2aa37d36305197242eb724229afc59468aa47c515dbfb8378d9fa6fafa88d8b90a2af6d1ed467b14
 
 install : $(TARGET)
 
-- 
2.53.0



                 reply	other threads:[~2026-06-24 10:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260624100948.3366703-1-matthias.fischer@ipfire.org \
    --to=matthias.fischer@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