From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 8c85098a875f4b5554ed481cf9e6d6db3cbf3042
Date: Fri, 20 Feb 2015 16:58:27 +0100 [thread overview]
Message-ID: <20150220155827.CAEF020345@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1463 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, master has been updated
via 8c85098a875f4b5554ed481cf9e6d6db3cbf3042 (commit)
from 4bf0d575277842efbadc5255b6c1a67fd49477ba (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 8c85098a875f4b5554ed481cf9e6d6db3cbf3042
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Feb 20 16:57:40 2015 +0100
core87: set correct version.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/87/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/87/update.sh b/config/rootfiles/core/87/update.sh
index a0bac4d..fea4488 100644
--- a/config/rootfiles/core/87/update.sh
+++ b/config/rootfiles/core/87/update.sh
@@ -57,7 +57,7 @@ function find_device() {
#
# Remove old core updates from pakfire cache to save space...
-core=86
+core=87
for (( i=1; i<=${core}; i++ ))
do
rm -f /var/cache/pakfire/core-upgrade-*-$i.ipfire
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-02-20 15:58 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=20150220155827.CAEF020345@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