From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e990e4273f4f9e493243c839e33328621b722968
Date: Sat, 05 May 2018 17:17:59 +0100 [thread overview]
Message-ID: <20180505161759.9A91B1081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 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 e990e4273f4f9e493243c839e33328621b722968 (commit)
from f1051b495269db1fb67c6d0e72628d4bfe3a910d (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 e990e4273f4f9e493243c839e33328621b722968
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat May 5 18:01:53 2018 +0200
core121: fix typo fileslist -> filelist
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/121/{fileslists => filelists}/files | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename config/rootfiles/core/121/{fileslists => filelists}/files (100%)
Difference in files:
diff --git a/config/rootfiles/core/121/fileslists/files b/config/rootfiles/core/121/filelists/files
similarity index 100%
rename from config/rootfiles/core/121/fileslists/files
rename to config/rootfiles/core/121/filelists/files
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-05-05 16:17 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=20180505161759.9A91B1081DF2@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