public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8e27b3ca86497fc1843749dcfb1f3eecf5a6afbd
Date: Tue, 04 Feb 2014 12:56:08 +0100	[thread overview]
Message-ID: <20140204115608.F067721069@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2128 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  8e27b3ca86497fc1843749dcfb1f3eecf5a6afbd (commit)
       via  6d72ff77e1f58fc7f0d6d4122ed231c47c5cdf13 (commit)
      from  fe30713604357bf8e7d62aa7e0d4c39402699938 (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 8e27b3ca86497fc1843749dcfb1f3eecf5a6afbd
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Feb 4 12:55:33 2014 +0100

    core76: Sort exclude file alphabetically.

commit 6d72ff77e1f58fc7f0d6d4122ed231c47c5cdf13
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Feb 4 12:51:21 2014 +0100

    Never include rc.local or firewall.local in a core update.

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/core/76/exclude | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

Difference in files:
diff --git a/config/rootfiles/core/76/exclude b/config/rootfiles/core/76/exclude
index 321a931..a468d0a 100644
--- a/config/rootfiles/core/76/exclude
+++ b/config/rootfiles/core/76/exclude
@@ -1,17 +1,19 @@
-srv/web/ipfire/html/proxy.pac
 boot/config.txt
-etc/udev/rules.d/30-persistent-network.rules
 etc/collectd.custom
-etc/shadow
 etc/ipsec.conf
 etc/ipsec.secrets
 etc/ipsec.user.conf
 etc/ipsec.user.secrets
-var/log/cache
-var/updatecache
 etc/localtime
-var/ipfire/ovpn
+etc/shadow
 etc/ssh/ssh_config
 etc/ssh/sshd_config
 etc/ssl/openssl.cnf
+etc/sysconfig/firewall.local
+etc/sysconfig/rc.local
+etc/udev/rules.d/30-persistent-network.rules
+srv/web/ipfire/html/proxy.pac
+var/ipfire/ovpn
+var/log/cache
 var/state/dhcp/dhcpd.leases
+var/updatecache


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-02-04 11:56 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=20140204115608.F067721069@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