From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0bdb63924b13d4e47db7cd03c6714cdfdd9280a9
Date: Wed, 04 Mar 2020 11:30:40 +0000 [thread overview]
Message-ID: <48XWsD49P3z2xq6@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1592 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 0bdb63924b13d4e47db7cd03c6714cdfdd9280a9 (commit)
from a344d3c902417a21b619c6e4f2a1aaf38e3044fe (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 0bdb63924b13d4e47db7cd03c6714cdfdd9280a9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Mar 4 10:44:50 2020 +0000
backup: Fix saving DNS settings
There was a typo in /var/ipfire/dns/servers and the settings
file was not explicitely included in the backup.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/backup/include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/backup/include b/config/backup/include
index d33dcf099..0153272f7 100644
--- a/config/backup/include
+++ b/config/backup/include
@@ -31,7 +31,7 @@
/var/ipfire/*/*.conf
/var/ipfire/*/config
/var/ipfire/dhcp/*
-/var/ipfire/dns/server
+/var/ipfire/dns
/var/ipfire/dnsforward/*
/var/ipfire/*/enable
/var/ipfire/*/*enable*
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-03-04 11:30 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=48XWsD49P3z2xq6@people01.haj.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