From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e4a5b2241725890fc9ac268c373d6c82ef337224
Date: Sun, 02 Jan 2022 14:41:19 +0000 [thread overview]
Message-ID: <4JRhQR69r0z2xKQ@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1532 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 e4a5b2241725890fc9ac268c373d6c82ef337224 (commit)
from 59e683df2524917dc443121fb2427ea779bc2062 (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 e4a5b2241725890fc9ac268c373d6c82ef337224
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Jan 2 14:35:07 2022 +0000
stage2: remove wrong curly brackets.
It is not allowed use this with only one parameter.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/stage2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/stage2 b/lfs/stage2
index daa98765e..3876060ce 100644
--- a/lfs/stage2
+++ b/lfs/stage2
@@ -132,7 +132,7 @@ endif
# Create /var dirs and files
-mkdir -v /var/{lock,log,mail,spool,empty}
- -mkdir -pv /var/{opt,cache,lib/{misc},local}
+ -mkdir -pv /var/{opt,cache,lib/misc,local}
-mkdir -pv /var/log/{counter,calamaris}
chown nobody.nobody /var/log/calamaris
touch /var/log/{btmp,lastlog,wtmp}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-01-02 14:41 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=4JRhQR69r0z2xKQ@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