From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 409b263f9f5136ebc5a368142b752205c34f5de9
Date: Wed, 27 Oct 2021 22:42:06 +0000 [thread overview]
Message-ID: <4HfkG6353Kz2xkV@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1542 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 409b263f9f5136ebc5a368142b752205c34f5de9 (commit)
from 832490f063f81a54ecb470caaa3fab8c3f73c12e (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 409b263f9f5136ebc5a368142b752205c34f5de9
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Tue Oct 26 19:01:28 2021 +0200
Core Update 161: fix typo (stronswan != strongswan)
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/161/filelists/{stronswan => strongswan} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename config/rootfiles/core/161/filelists/{stronswan => strongswan} (100%)
Difference in files:
diff --git a/config/rootfiles/core/161/filelists/stronswan b/config/rootfiles/core/161/filelists/strongswan
similarity index 100%
rename from config/rootfiles/core/161/filelists/stronswan
rename to config/rootfiles/core/161/filelists/strongswan
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-10-27 22:42 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=4HfkG6353Kz2xkV@people01.haj.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