From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 5663d181bb599806acc2413affa6a3a58c3518a0
Date: Mon, 28 Jul 2014 11:59:02 +0200 [thread overview]
Message-ID: <20140728095902.949D821264@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1790 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 5663d181bb599806acc2413affa6a3a58c3518a0 (commit)
via ff601bca1cf58d3d399a80ae78ebaf8b2e972ba2 (commit)
from 2db3b9b15645ff9dcb67ba55d9837faade0b7e69 (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 5663d181bb599806acc2413affa6a3a58c3518a0
Merge: 2db3b9b ff601bc
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jul 28 11:56:17 2014 +0200
Merge remote-tracking branch 'stevee/transmission-2.84'
commit ff601bca1cf58d3d399a80ae78ebaf8b2e972ba2
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Thu Jul 10 19:32:03 2014 +0200
transmission: Update to 2.84.
This is a minor update to the latest stable version.
-----------------------------------------------------------------------
Summary of changes:
transmission/transmission.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/transmission/transmission.nm b/transmission/transmission.nm
index 5ccd508..8790aca 100644
--- a/transmission/transmission.nm
+++ b/transmission/transmission.nm
@@ -4,7 +4,7 @@
###############################################################################
name = transmission
-version = 2.80
+version = 2.84
release = 1
groups = Internet/P2P
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2014-07-28 9:59 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=20140728095902.949D821264@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