From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 2aecef3e59f4e63dfb781b4e2493edbd6225268d
Date: Fri, 23 Aug 2013 17:38:05 +0200 [thread overview]
Message-ID: <20130823153805.D358B20542@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1674 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 2aecef3e59f4e63dfb781b4e2493edbd6225268d (commit)
from 127b7c43d057173345b261d36ec3384ad159d34c (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 2aecef3e59f4e63dfb781b4e2493edbd6225268d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Aug 23 17:37:42 2013 +0200
transmission: update to 2.82.
-----------------------------------------------------------------------
Summary of changes:
lfs/transmission | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/transmission b/lfs/transmission
index 9d5dfa5..3c1368d 100644
--- a/lfs/transmission
+++ b/lfs/transmission
@@ -24,7 +24,7 @@
include Config
-VER = 2.81
+VER = 2.82
THISAPP = transmission-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = transmission
-PAK_VER = 8
+PAK_VER = 9
DEPS = "libevent2"
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = db1ad10ecff07150486dab2365ccb3a8
+$(DL_FILE)_MD5 = a5ef870c0410b12d10449c2d36fa4661
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-08-23 15:38 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=20130823153805.D358B20542@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