From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c2de1bd7a59601926e2dad7e361a8d0b8379e87d
Date: Sat, 06 Aug 2022 07:22:20 +0000 [thread overview]
Message-ID: <4M0DSD4zM0z2xNT@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4565 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via c2de1bd7a59601926e2dad7e361a8d0b8379e87d (commit)
via 3aa645a87d781b5a8ecf514d4d2844d9798da578 (commit)
from f9d939b7f3dad39ebc2d2b19beb5b23fa57278be (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit c2de1bd7a59601926e2dad7e361a8d0b8379e87d
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sat Aug 6 07:22:02 2022 +0000
Core Update 170: Ship nano
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
commit 3aa645a87d781b5a8ecf514d4d2844d9798da578
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Fri Aug 5 22:32:01 2022 +0200
nano: Update to 6.4
For details see:
https://www.nano-editor.org/news.php
"Changes between v6.3 and v6.4:
------------------------------
Benno Schulenberg (24):
bump version numbers and add a news item for the 6.4 release
display: remember text and column positions when softwrapping a line
docs: concisely describe how the linter behaves
docs: remove the two notices about the changed defaults
docs: rename README.GIT to README.hacking, so it's clearer what is meant
docs: stop mentioning the obsoleted keywords that were removed
files: designate the root directory with a simple "/", not with "//"
formatter: instead of leaving curses, use full_refresh() to wipe messages
gnulib: update to its current upstream state
help: reshuffle two shortcuts so that more help-line items are paired
options: stop accepting -z, as --suspendable has been dropped too
rcfile: remove five obsolete or deprecated keywords
syntax: default: do not colorize a square or angle bracket after a URL
syntax: perl: add missing keywords, and reduce the length of some lines
syntax: python: mention an alternative linter in a comment
tweaks: add a missing word to a news item
tweaks: add a translator hint
tweaks: improve a comment, and reshuffle two functions plus some lines
tweaks: put each regex on separate line, to better show many keywords
tweaks: rename a variable, to not be the same as a function name
tweaks: rename two variables, to not contain the name of another
tweaks: reshuffle a description and rewrap another
tweaks: reshuffle a few lines, to group things better
version: condense the copyright message, to not dominate the output
LIU Hao (1):
build: ignore errors from `git describe`"
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/167 => core/170}/filelists/nano | 0
lfs/nano | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
copy config/rootfiles/{oldcore/167 => core/170}/filelists/nano (100%)
Difference in files:
diff --git a/config/rootfiles/core/170/filelists/nano b/config/rootfiles/core/170/filelists/nano
new file mode 120000
index 000000000..2f07279c0
--- /dev/null
+++ b/config/rootfiles/core/170/filelists/nano
@@ -0,0 +1 @@
+../../../common/nano
\ No newline at end of file
diff --git a/lfs/nano b/lfs/nano
index 05e63528c..5dc6981b0 100644
--- a/lfs/nano
+++ b/lfs/nano
@@ -24,7 +24,7 @@
include Config
-VER = 6.3
+VER = 6.4
THISAPP = nano-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 92ef2acac0dacebc0bf8364bfee928a8394d8e4323e622ad6ba9d35bebd18d3976ab0ca747f7c9b5597874775b44ba4b5560e7392606aa68736158c2bda62b92
+$(DL_FILE)_BLAKE2 = b59ff7a741ce4c8b31afdbbfaf1d704cccbceddcd7f1421f30a6dd40495ec456ca891aeb9777c070c6cce4e9c594f83798ff0cdacdfe06e81b0aa0b700033da3
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-08-06 7:22 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=4M0DSD4zM0z2xNT@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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