From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 716c4751e71f63f923a3cb0ed32ad17b4fbdb1d0
Date: Tue, 03 Jul 2018 16:06:42 +0100 [thread overview]
Message-ID: <20180703150642.D40FD1081BA5@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1510 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 716c4751e71f63f923a3cb0ed32ad17b4fbdb1d0 (commit)
from 904ae7929ad191d379d2fa6a8ac0ca435e9edd92 (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 716c4751e71f63f923a3cb0ed32ad17b4fbdb1d0
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Jul 3 16:03:37 2018 +0100
spice-protocol: rootfile update
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/spice-protocol | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/common/spice-protocol b/config/rootfiles/common/spice-protocol
index 586b8e9ac..26cdc2102 100644
--- a/config/rootfiles/common/spice-protocol
+++ b/config/rootfiles/common/spice-protocol
@@ -16,4 +16,5 @@
#usr/include/spice-1/spice/types.h
#usr/include/spice-1/spice/vd_agent.h
#usr/include/spice-1/spice/vdi_dev.h
+#usr/share/pkgconfig
#usr/share/pkgconfig/spice-protocol.pc
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-07-03 15:06 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=20180703150642.D40FD1081BA5@git01.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