From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 65a61d88c8a9d73c3315f4ea07a0d5f714ceb2d4
Date: Fri, 29 Jul 2016 18:00:26 +0100 [thread overview]
Message-ID: <20160729170026.4FA8B1081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1825 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 65a61d88c8a9d73c3315f4ea07a0d5f714ceb2d4 (commit)
via 9a300ee8b5d142f1b3d7a47be64be03151493067 (commit)
from 0c265f57175644c55431490a2aa10b860eabc26d (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 65a61d88c8a9d73c3315f4ea07a0d5f714ceb2d4
Merge: 9a300ee 0c265f5
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jul 29 18:58:56 2016 +0200
Merge branch 'next' of git.ipfire.org:/pub/git/ipfire-2.x into next
commit 9a300ee8b5d142f1b3d7a47be64be03151493067
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jul 29 18:57:49 2016 +0200
core104: ship screen
old binary is linked against libshadow.0*
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/89 => core/104}/filelists/screen | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/89 => core/104}/filelists/screen (100%)
Difference in files:
diff --git a/config/rootfiles/core/104/filelists/screen b/config/rootfiles/core/104/filelists/screen
new file mode 120000
index 0000000..81008f4
--- /dev/null
+++ b/config/rootfiles/core/104/filelists/screen
@@ -0,0 +1 @@
+../../../common/screen
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-07-29 17:00 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=20160729170026.4FA8B1081BA6@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