From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. eb915ddd55640ae2856458f86f9013fc8a95fe4c
Date: Sat, 26 Jan 2013 20:24:20 +0100 [thread overview]
Message-ID: <20130126192420.D6C0D20132@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1399 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 eb915ddd55640ae2856458f86f9013fc8a95fe4c (commit)
from 92d75b2ed53e72427beab0dbda8f06577d42e4c5 (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 eb915ddd55640ae2856458f86f9013fc8a95fe4c
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Jan 26 20:23:38 2013 +0100
core66: remove proxy-cache from the updater/backup.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/66/exclude | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/66/exclude b/config/rootfiles/core/66/exclude
index 0b54d05..18141fd 100644
--- a/config/rootfiles/core/66/exclude
+++ b/config/rootfiles/core/66/exclude
@@ -6,6 +6,7 @@ etc/ipsec.conf
etc/ipsec.secrets
etc/ipsec.user.conf
etc/ipsec.user.secrets
+var/log/cache
var/updatecache
etc/localtime
var/ipfire/ovpn
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-01-26 19:24 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=20130126192420.D6C0D20132@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