From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a1de9f6fc9cd011cc33708bae31a731394b6d26a
Date: Sat, 01 Oct 2016 19:00:57 +0100 [thread overview]
Message-ID: <20161001180057.AA5F61078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1517 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 a1de9f6fc9cd011cc33708bae31a731394b6d26a (commit)
from 80bc60228b53635aa3e742467195b63adff30c59 (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 a1de9f6fc9cd011cc33708bae31a731394b6d26a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Oct 1 18:56:42 2016 +0100
core106: Ship updated /etc/login.defs
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/106/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/106/filelists/files b/config/rootfiles/core/106/filelists/files
index fdd8f89..1d5d4df 100644
--- a/config/rootfiles/core/106/filelists/files
+++ b/config/rootfiles/core/106/filelists/files
@@ -1,5 +1,6 @@
etc/system-release
etc/issue
+etc/login.defs
etc/rc.d/init.d/dhcp
etc/rc.d/init.d/network
etc/rc.d/init.d/networking/red.down/05-update-dns-forwarders
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-10-01 18: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=20161001180057.AA5F61078E81@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