From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] Core Update 161: fix typo (stronswan != strongswan)
Date: Tue, 26 Oct 2021 19:01:28 +0200 [thread overview]
Message-ID: <c197da0b-a491-367a-ed40-972f5cc60de2@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
config/rootfiles/core/161/filelists/{stronswan => strongswan} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename config/rootfiles/core/161/filelists/{stronswan => strongswan} (100%)
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
--
2.26.2
reply other threads:[~2021-10-26 17:01 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=c197da0b-a491-367a-ed40-972f5cc60de2@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@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