From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. dccbe309d2b568147c47a4d37c59b5686a7babbe
Date: Wed, 11 Nov 2015 15:01:54 +0100 [thread overview]
Message-ID: <20151111140154.6CD2521753@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1340 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 dccbe309d2b568147c47a4d37c59b5686a7babbe (commit)
from 4e17785fc101be1bef918fe5c739a2aa8e68075c (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 dccbe309d2b568147c47a4d37c59b5686a7babbe
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Nov 11 15:01:13 2015 +0100
core96: add pakfire changes to updater
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/96/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/96/filelists/files b/config/rootfiles/core/96/filelists/files
index 409e5fe..c9f5f4e 100644
--- a/config/rootfiles/core/96/filelists/files
+++ b/config/rootfiles/core/96/filelists/files
@@ -1,2 +1,3 @@
etc/system-release
etc/issue
+opt/pakfire/lib/functions.pl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-11-11 14:01 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=20151111140154.6CD2521753@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