From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 24f2144dd26388215ab204b0e48217ffa4d40bfb
Date: Sat, 12 Dec 2015 12:36:33 +0100 [thread overview]
Message-ID: <20151212113634.09C362143E@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1875 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 24f2144dd26388215ab204b0e48217ffa4d40bfb (commit)
from ffeaaef6182adc81f01684a98cd1f5975d22b4be (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 24f2144dd26388215ab204b0e48217ffa4d40bfb
Author: root <root(a)ipfire.localdomain>
Date: Sat Dec 12 12:35:24 2015 +0100
ramdisk: Fix copying files
The shell expansion wasn't used because of the quotation marks.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/init.d/functions | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/src/initscripts/init.d/functions b/src/initscripts/init.d/functions
index fc4d8a4..232d523 100644
--- a/src/initscripts/init.d/functions
+++ b/src/initscripts/init.d/functions
@@ -756,7 +756,7 @@ mount_ramdisk() {
mount -t tmpfs none "${path_tmpfs}"
# Restore ramdisk content
- cp -pR "${path}/*" "${path_tmpfs}"
+ cp -pR ${path}/* "${path_tmpfs}"
# Move ramdisk to final destination
mount --move "${path_tmpfs}" "${path}"
@@ -777,7 +777,7 @@ umount_ramdisk() {
mount --move "${path}" "${path_tmpfs}"
# Backup ramdisk content
- cp -pR "${path_tmpfs}/*" "${path}"
+ cp -pR ${path_tmpfs}/* "${path}"
# Destroy the ramdisk
umount "${path_tmpfs}"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-12-12 11:36 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=20151212113634.09C362143E@argus.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