From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 24159f095246659fed4bb581384fa91784d3359e
Date: Mon, 25 Jul 2016 17:26:01 +0100 [thread overview]
Message-ID: <20160725162602.107321081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1554 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 24159f095246659fed4bb581384fa91784d3359e (commit)
from c48a24dc14da1322dae72511c3e4c021602cf005 (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 24159f095246659fed4bb581384fa91784d3359e
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Fri Jul 22 22:23:24 2016 +0200
nano 2.6.1: fix in rootfile
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/nano | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/packages/nano b/config/rootfiles/packages/nano
index 3582f36..f8171b4 100644
--- a/config/rootfiles/packages/nano
+++ b/config/rootfiles/packages/nano
@@ -49,6 +49,7 @@ usr/share/nano/postgresql.nanorc
usr/share/nano/pov.nanorc
usr/share/nano/python.nanorc
usr/share/nano/ruby.nanorc
+usr/share/nano/rust.nanorc
usr/share/nano/sh.nanorc
usr/share/nano/spec.nanorc
usr/share/nano/tcl.nanorc
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-07-25 16:26 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=20160725162602.107321081BA6@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