From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core119, created. f0869181e846cf235eca2d74eaf4c219740f3de8
Date: Sat, 24 Feb 2018 13:38:33 +0000 [thread overview]
Message-ID: <20180224133833.C54C5106D063@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1520 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, core119 has been created
at f0869181e846cf235eca2d74eaf4c219740f3de8 (commit)
- Log -----------------------------------------------------------------
commit f0869181e846cf235eca2d74eaf4c219740f3de8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Feb 24 14:31:54 2018 +0100
core119: set pakfire version to 119
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
commit 4038a839612438a43e3771a1f534218890a64dc4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Feb 24 14:30:19 2018 +0100
core119: restart init after unpack new glibc
this is needed to prevent problems at unmout filesystems at reboot.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
commit c560b903a9ef9efb7d93a503da4667adbec94ccc
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Feb 23 20:43:41 2018 +0000
core119: Ship updated libgcc_s.so.1
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit 2edff5e9700908a3c91a8f0a66862f420faefebd
Merge: 6af8fa9e0 83d6101b9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Feb 21 12:06:21 2018 +0000
Merge remote-tracking branch 'origin/next'
-----------------------------------------------------------------------
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-02-24 13:38 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=20180224133833.C54C5106D063@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