From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: Re: [PATCH] tests: mkfs.ext3 image-file needs option -F
Date: Fri, 12 Feb 2016 17:25:54 +0100 [thread overview]
Message-ID: <201602121725.54903.sweet_f_a@gmx.de> (raw)
In-Reply-To: <1455294198-25046-1-git-send-email-sweet_f_a@gmx.de>
Oops, by accident I've used the wrong --in-reply-to from my shell
history.
On Friday 12 February 2016, Ruediger Meier wrote:
> From: Ruediger Meier <ruediger.meier@ga-group.nl>
>
> Maybe on newer systems it's not needed anymore.
>
> Signed-off-by: Ruediger Meier <ruediger.meier@ga-group.nl>
> ---
> tests/ts/mount/fstab-loop | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/ts/mount/fstab-loop b/tests/ts/mount/fstab-loop
> index 3178b95..9e17943 100755
> --- a/tests/ts/mount/fstab-loop
> +++ b/tests/ts/mount/fstab-loop
> @@ -30,7 +30,7 @@ ts_check_prog "mkfs.ext3"
>
> IMG=$(ts_image_init)
>
> -mkfs.ext3 $IMG &> /dev/null || ts_die "Cannot make ext3 on $DEVICE"
> +mkfs.ext3 -F $IMG &> /dev/null || ts_die "Cannot make ext3 on $IMG"
>
> [ -d "$TS_MOUNTPOINT-1" ] || mkdir -p $TS_MOUNTPOINT-1
> [ -d "$TS_MOUNTPOINT-2" ] || mkdir -p $TS_MOUNTPOINT-2
next prev parent reply other threads:[~2016-02-12 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 0:03 script, broken test options/return Ruediger Meier
2015-07-02 8:23 ` Karel Zak
2015-07-02 8:32 ` Karel Zak
2015-07-02 10:06 ` Ruediger Meier
2015-07-02 10:10 ` [PATCH] script: evaluate errno only if read() sets it Ruediger Meier
2015-07-02 10:21 ` Ruediger Meier
2015-07-03 8:04 ` Karel Zak
2015-07-03 10:33 ` Ruediger Meier
2016-02-12 16:23 ` [PATCH] tests: mkfs.ext3 image-file needs option -F Ruediger Meier
2016-02-12 16:25 ` Ruediger Meier [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-12 16:23 [PATCH] tests: add test for loop option in fstab Ruediger Meier
2016-02-12 16:28 ` [PATCH] tests: mkfs.ext3 image-file needs option -F Ruediger Meier
2016-02-12 17:09 ` Karel Zak
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=201602121725.54903.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.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