From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a0168f9fca199e78bf88ab263deaec3a2c8e977e
Date: Sat, 08 Apr 2017 14:42:33 +0100 [thread overview]
Message-ID: <20170408134233.81F0310853C3@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1550 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 a0168f9fca199e78bf88ab263deaec3a2c8e977e (commit)
from b3ee263b07d24c115614e2d5ceb909f1afe10c80 (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 a0168f9fca199e78bf88ab263deaec3a2c8e977e
Author: Timo Eissler <timo.eissler(a)ipfire.org>
Date: Fri Apr 7 21:59:40 2017 +0200
nmap: remove uninstall_ndiff from rootfile
Signed-off-by: Timo Eissler <timo.eissler(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/nmap | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/packages/nmap b/config/rootfiles/packages/nmap
index 5d0e50d..111610a 100644
--- a/config/rootfiles/packages/nmap
+++ b/config/rootfiles/packages/nmap
@@ -1,7 +1,7 @@
usr/bin/ndiff
usr/bin/nmap
usr/bin/nping
-usr/bin/uninstall_ndiff
+#usr/bin/uninstall_ndiff
usr/lib/python2.7/site-packages/ndiff.py
usr/lib/python2.7/site-packages/ndiff.pyc
#usr/share/man/de/man1/nmap.1
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-04-08 13:42 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=20170408134233.81F0310853C3@git01.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