From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a0ef4c5bb6f17494172148fe0a5b09e6278c0e92
Date: Thu, 07 Feb 2013 17:07:31 +0100 [thread overview]
Message-ID: <20130207160732.117C0200DA@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1718 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 a0ef4c5bb6f17494172148fe0a5b09e6278c0e92 (commit)
from 0aa93f5b11a57236f523714373e1abca25caaa65 (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 a0ef4c5bb6f17494172148fe0a5b09e6278c0e92
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Feb 7 17:06:13 2013 +0100
bind: Ship dig.
References #10151.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/bind | 2 +-
config/rootfiles/core/66/filelists/bind | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
create mode 120000 config/rootfiles/core/66/filelists/bind
Difference in files:
diff --git a/config/rootfiles/common/bind b/config/rootfiles/common/bind
index db6bdab..df66853 100644
--- a/config/rootfiles/common/bind
+++ b/config/rootfiles/common/bind
@@ -1,4 +1,4 @@
-#usr/bin/dig
+usr/bin/dig
usr/bin/host
usr/bin/nslookup
usr/bin/nsupdate
diff --git a/config/rootfiles/core/66/filelists/bind b/config/rootfiles/core/66/filelists/bind
new file mode 120000
index 0000000..48a0eba
--- /dev/null
+++ b/config/rootfiles/core/66/filelists/bind
@@ -0,0 +1 @@
+../../../common/bind
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-02-07 16:07 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=20130207160732.117C0200DA@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