From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 5354877414fd0703556d481b299ef9635dd5d99b
Date: Thu, 24 Mar 2016 20:13:04 +0000 [thread overview]
Message-ID: <20160324201305.4B30F1081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1509 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 5354877414fd0703556d481b299ef9635dd5d99b (commit)
from b4a362e851b1eb4adc7cd36ac365256edcfef426 (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 5354877414fd0703556d481b299ef9635dd5d99b
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Mar 24 19:31:59 2016 +0000
Revert "ghostscript: Update to 9.18"
This reverts commit 127490ed041d0e9b4e9de4b4a9a0941edf8e2dd0.
-----------------------------------------------------------------------
Summary of changes:
ghostscript/ghostscript.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/ghostscript/ghostscript.nm b/ghostscript/ghostscript.nm
index 649bedb..9bda982 100644
--- a/ghostscript/ghostscript.nm
+++ b/ghostscript/ghostscript.nm
@@ -4,7 +4,7 @@
###############################################################################
name = ghostscript
-version = 9.18
+version = 9.14
release = 1
groups = Applications/Printing
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-03-24 20:13 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=20160324201305.4B30F1081BA6@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