From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core133, updated. bc051eac54375a7f90b1d157414610f58de8c34a
Date: Sat, 15 Jun 2019 15:51:53 +0100 [thread overview]
Message-ID: <20190615145153.98C2684FDC0@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1464 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, core133 has been updated
via bc051eac54375a7f90b1d157414610f58de8c34a (commit)
from f081e454a6a0074a7ded39bbe0eb5eadd8e3ecf3 (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 bc051eac54375a7f90b1d157414610f58de8c34a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Jun 14 06:22:52 2019 +0100
core133: Ship jansson in update
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/133/filelists/jansson | 1 +
1 file changed, 1 insertion(+)
create mode 120000 config/rootfiles/core/133/filelists/jansson
Difference in files:
diff --git a/config/rootfiles/core/133/filelists/jansson b/config/rootfiles/core/133/filelists/jansson
new file mode 120000
index 000000000..21f73bd0c
--- /dev/null
+++ b/config/rootfiles/core/133/filelists/jansson
@@ -0,0 +1 @@
+../../../common/jansson
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-06-15 14:51 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=20190615145153.98C2684FDC0@people01.i.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