From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core105, updated. e4ee7f0317547aacd36b9b5d31f9eb659ab5f455
Date: Thu, 22 Sep 2016 17:16:15 +0100 [thread overview]
Message-ID: <20160922161616.0A1681078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1424 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, core105 has been updated
via e4ee7f0317547aacd36b9b5d31f9eb659ab5f455 (commit)
from cd805ced09c2e203e7e6b874b7b96fb5e86a11b5 (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 e4ee7f0317547aacd36b9b5d31f9eb659ab5f455
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Sep 22 17:44:06 2016 +0200
core105: fix rootfile.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/105/filelists/files | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/105/filelists/files b/config/rootfiles/core/105/filelists/files
index 95f6e10..409e5fe 100644
--- a/config/rootfiles/core/105/filelists/files
+++ b/config/rootfiles/core/105/filelists/files
@@ -1,2 +1,2 @@
etc/system-release
-etc/issue
\ No newline at end of file
+etc/issue
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-09-22 16:16 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=20160922161616.0A1681078E81@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