From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 853c9538e466286d18cee6b8b11368d2e583056e
Date: Fri, 11 Aug 2023 11:00:28 +0000 [thread overview]
Message-ID: <4RMgn90YWNz2xVZ@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1420 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 853c9538e466286d18cee6b8b11368d2e583056e (commit)
from 58cd7839b50c772a10637a246c8631285a43fce7 (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 853c9538e466286d18cee6b8b11368d2e583056e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Aug 11 10:59:49 2023 +0000
nmap: Bump release once again
https://lists.ipfire.org/pipermail/development/2023-August/016285.html
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/nmap | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/nmap b/lfs/nmap
index 2b1b97dab..36a348be4 100644
--- a/lfs/nmap
+++ b/lfs/nmap
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = nmap
-PAK_VER = 17
+PAK_VER = 18
DEPS =
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-08-11 11: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=4RMgn90YWNz2xVZ@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