From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: nmap PAK_VER bumped from 15 to 16 in three separate commits
Date: Tue, 08 Aug 2023 21:05:17 +0200 [thread overview]
Message-ID: <a74c1819-f7f3-470e-97e1-ad5db3be7980@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Hi All,
Don't know if git will cope with this or not but I submitted an nmap/ncat update which was merged on 24th July and incremented the PAK_VER from 15 to 16
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=a6b7832024ca58d689e59ff0a12442f573d2dfff
Today Matthias submitted a patch to increment the PAK_VER of nmap from 15 to 16.
Then a bit later Michael raised a patch on CU177 that incremented the PAK_VER of nmap from 15 to 16.
So there are three commits each of which increment the PAK_VER of the same package in the identical way.
Regards,
Adolf.
next reply other threads:[~2023-08-08 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 19:05 Adolf Belka [this message]
2023-08-11 11:00 ` 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=a74c1819-f7f3-470e-97e1-ad5db3be7980@ipfire.org \
--to=adolf.belka@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