From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 28bee14eccbc3e2cada73cbbe84634e070c8c8bc
Date: Sun, 08 Nov 2015 10:04:46 +0100 [thread overview]
Message-ID: <20151108090446.4F9D12157A@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1427 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 28bee14eccbc3e2cada73cbbe84634e070c8c8bc (commit)
from c88002c48b8011dfec3aefe66f66769e786db11b (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 28bee14eccbc3e2cada73cbbe84634e070c8c8bc
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Nov 8 10:04:13 2015 +0100
core95: add ipset to updater.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/95/filelists/ipset | 1 +
1 file changed, 1 insertion(+)
create mode 120000 config/rootfiles/core/95/filelists/ipset
Difference in files:
diff --git a/config/rootfiles/core/95/filelists/ipset b/config/rootfiles/core/95/filelists/ipset
new file mode 120000
index 0000000..2b43691
--- /dev/null
+++ b/config/rootfiles/core/95/filelists/ipset
@@ -0,0 +1 @@
+../../../common/ipset
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-11-08 9:04 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=20151108090446.4F9D12157A@argus.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