From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. cd022294d9d4926b3c3609ba8ccdca2652eea46e
Date: Thu, 29 Nov 2018 13:17:34 +0000 [thread overview]
Message-ID: <20181129131734.6434384FDD5@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1442 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 cd022294d9d4926b3c3609ba8ccdca2652eea46e (commit)
from 97431824725e6c6625d5f518a97a950b6d6a91ad (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 cd022294d9d4926b3c3609ba8ccdca2652eea46e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Nov 29 13:16:37 2018 +0000
nfs: Fix build
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/nfs | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/lfs/nfs b/lfs/nfs
index 4083073e2..40c17b788 100644
--- a/lfs/nfs
+++ b/lfs/nfs
@@ -105,6 +105,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
$(call INSTALL_INITSCRIPT,nfs-server)
# Install configuration
+ mkdir -pv $(CONFIG_ROOT)/nfs
install -v -m 644 $(DIR_SRC)/config/cfgroot/nfs-server $(CONFIG_ROOT)/nfs/nfs-server
# Install backup include
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-11-29 13: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=20181129131734.6434384FDD5@people01.i.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