From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core96, updated. 2be37981915534c01de54d36bed109acb21608bf
Date: Mon, 01 Feb 2016 20:57:30 +0100 [thread overview]
Message-ID: <20160201195730.C5BC72153D@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1435 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, core96 has been updated
via 2be37981915534c01de54d36bed109acb21608bf (commit)
from 23c6a8d710f577b503b5fd14d4067f40eaf508ff (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 2be37981915534c01de54d36bed109acb21608bf
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Feb 1 20:32:10 2016 +0100
core96: exclude /boot/grub/grub.cfg
this fixes xen problems.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/96/exclude | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/96/exclude b/config/rootfiles/core/96/exclude
index 8e446ce..dd390dc 100644
--- a/config/rootfiles/core/96/exclude
+++ b/config/rootfiles/core/96/exclude
@@ -1,4 +1,5 @@
boot/config.txt
+boot/grub/grub.cfg
etc/alternatives
etc/collectd.custom
etc/default/grub
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-02-01 19:57 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=20160201195730.C5BC72153D@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