From: Dan McGrath <danmcgrath.ca@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Dan McGrath <danmcgrath.ca@gmail.com>
Subject: [PATCH] btrfs-progs: No-op when called as fsck.btrfsck
Date: Mon, 15 Apr 2013 09:47:08 -0400 [thread overview]
Message-ID: <1366033629-25121-1-git-send-email-danmcgrath.ca@gmail.com> (raw)
Hi,
I thought that I would attempt a quick little patch that will make btrfsck into
a No-op when called as fsck.btrfsck.
The reasoning is that the FAQ states that it is recommended and safe to do so,
and the current 12.04 version of Ubuntu just symlinks fsck.btrfsck to btrfsck
instead of /bin/true.
PS - Apologies if I mess this git send-email up!
Dan McGrath (1):
btrfs-progs: No-op when called as fsck.btrfsck
btrfs.c | 2 ++
1 file changed, 2 insertions(+)
--
1.7.9.5
next reply other threads:[~2013-04-15 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 13:47 Dan McGrath [this message]
2013-04-15 13:47 ` [PATCH] btrfs-progs: No-op when called as fsck.btrfsck Dan McGrath
2013-04-15 14:03 ` Jan Alexander Steffens
2013-04-15 14:10 ` Dan McGrath
2013-04-15 16:38 ` Eric Sandeen
2013-04-15 16:45 ` Dan McGrath
2013-04-15 17:01 ` Eric Sandeen
2013-04-15 17:23 ` Dan McGrath
2013-04-15 18:59 ` Zach Brown
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=1366033629-25121-1-git-send-email-danmcgrath.ca@gmail.com \
--to=danmcgrath.ca@gmail.com \
--cc=linux-btrfs@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