From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 340a567eae8e9a1be908c13e67626d278f32224c
Date: Fri, 08 Nov 2013 14:55:44 +0100 [thread overview]
Message-ID: <20131108135544.E453720FAD@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1740 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, fifteen has been updated
via 340a567eae8e9a1be908c13e67626d278f32224c (commit)
from cbc6219852bbb1162469e5a002e1c923e7e4fad9 (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 340a567eae8e9a1be908c13e67626d278f32224c
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Nov 8 14:55:23 2013 +0100
Ship paxctl with the distribution.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/paxctl | 2 +-
config/rootfiles/core/fifteen/filelists/paxctl | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
create mode 120000 config/rootfiles/core/fifteen/filelists/paxctl
Difference in files:
diff --git a/config/rootfiles/common/paxctl b/config/rootfiles/common/paxctl
index 4faecba..c9135a8 100644
--- a/config/rootfiles/common/paxctl
+++ b/config/rootfiles/common/paxctl
@@ -1,2 +1,2 @@
-#sbin/paxctl
+sbin/paxctl
#usr/share/man/man1/paxctl.1
diff --git a/config/rootfiles/core/fifteen/filelists/paxctl b/config/rootfiles/core/fifteen/filelists/paxctl
new file mode 120000
index 0000000..dda8d9f
--- /dev/null
+++ b/config/rootfiles/core/fifteen/filelists/paxctl
@@ -0,0 +1 @@
+../../../common/paxctl
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-11-08 13:55 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=20131108135544.E453720FAD@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