From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 901f6b7c292da9829a7ff4cf04caad48128bf87e
Date: Thu, 21 Jul 2022 08:00:05 +0000 [thread overview]
Message-ID: <4LpQ396RXxz2y0Q@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2432 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 901f6b7c292da9829a7ff4cf04caad48128bf87e (commit)
from efd00f07f96ff4074427de7089a25c5b34738d3a (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 901f6b7c292da9829a7ff4cf04caad48128bf87e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Jul 21 07:59:43 2022 +0000
ncurses: Ship tmux terminfo
Fixes: #12905
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/ncurses | 6 +++---
config/rootfiles/core/170/filelists/files | 3 +++
2 files changed, 6 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/ncurses b/config/rootfiles/common/ncurses
index 323c5c055..edd73b219 100644
--- a/config/rootfiles/common/ncurses
+++ b/config/rootfiles/common/ncurses
@@ -3056,9 +3056,9 @@ usr/share/terminfo/t/teraterm2.3
#usr/share/terminfo/t/ti931
#usr/share/terminfo/t/ti_ansi
#usr/share/terminfo/t/tkterm
-#usr/share/terminfo/t/tmux
-#usr/share/terminfo/t/tmux-256color
-#usr/share/terminfo/t/tmux-direct
+usr/share/terminfo/t/tmux
+usr/share/terminfo/t/tmux-256color
+usr/share/terminfo/t/tmux-direct
#usr/share/terminfo/t/tn1200
#usr/share/terminfo/t/tn300
#usr/share/terminfo/t/trs16
diff --git a/config/rootfiles/core/170/filelists/files b/config/rootfiles/core/170/filelists/files
index cdfb44946..25f262eb7 100644
--- a/config/rootfiles/core/170/filelists/files
+++ b/config/rootfiles/core/170/filelists/files
@@ -8,6 +8,9 @@ srv/web/ipfire/cgi-bin/logs.cgi/showrequestfromblocklist.dat
usr/lib/firewall/rules.pl
usr/local/bin/setaliases
usr/local/bin/update-ipblocklists
+usr/share/terminfo/t/tmux
+usr/share/terminfo/t/tmux-256color
+usr/share/terminfo/t/tmux-direct
var/ipfire/backup/bin/backup.pl
var/ipfire/backup/include
var/ipfire/ipblocklist-functions.pl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-07-21 8:00 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=4LpQ396RXxz2y0Q@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