From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 8db6df934338535beafaca34cc7a268f421c4397
Date: Sun, 23 Oct 2016 23:40:28 +0100 [thread overview]
Message-ID: <20161023224029.23FF41081BA5@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1786 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 3.x development tree".
The branch, master has been updated
via 8db6df934338535beafaca34cc7a268f421c4397 (commit)
from c5d6f3e190aaa5d4238b05d5cc523c5e6c8d3b44 (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 8db6df934338535beafaca34cc7a268f421c4397
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Oct 23 23:37:09 2016 +0100
quagga: Update to 1.1.0
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
quagga/quagga.nm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/quagga/quagga.nm b/quagga/quagga.nm
index 57965a3..5c40acd 100644
--- a/quagga/quagga.nm
+++ b/quagga/quagga.nm
@@ -4,8 +4,8 @@
###############################################################################
name = quagga
-version = 1.0.20160315
-release = 2
+version = 1.1.0
+release = 1
groups = Networking/Routing
url = http://www.quagga.net/
@@ -21,7 +21,6 @@ description
end
source_dl = http://download.savannah.gnu.org/releases/quagga/
-sources = %{thisapp}.tar.xz
build
requires
@@ -29,6 +28,7 @@ build
net-snmp-devel
readline-devel
systemd-units
+ texinfo
end
prepare_cmds
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-10-23 22:40 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=20161023224029.23FF41081BA5@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