From: James Daniel Smith <smithjd15@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-progs
Date: Thu, 19 Apr 2012 16:26:55 -0600 [thread overview]
Message-ID: <14055805.ZYpkv1DjiU@linux-lt2.site> (raw)
[-- Attachment #1: Type: text/plain, Size: 169 bytes --]
Here are a couple of cleanup patches. Please apply newline first.
Thanks!
--
James Smith
CT.Networks
I.T. Consultant / Networking Systems Analyst
smithjd15@gmail.com
[-- Attachment #2: btrfscleanup.diff --]
[-- Type: text/x-patch, Size: 1136 bytes --]
--- btrfs-progs/btrfs.c 2012-04-19 15:34:20.188146191 -0600
+++ btrfs.c 2012-04-19 15:37:43.680140829 -0600
@@ -105,7 +105,7 @@
{ do_resize, 2,
"filesystem resize", "[+/-]<newsize>[gkm]|max <filesystem>\n"
"Resize the file system. If 'max' is passed, the filesystem\n"
- "will occupe all available space on the device.",
+ "will occupy all available space on the device.",
NULL
},
{ do_show_filesystem, 999,
@@ -155,7 +155,7 @@
},
{ do_scan, 999,
"device scan", "[<device>...]\n"
- "Scan all device for or the passed device for a btrfs\n"
+ "Scan all devices or the passed device for a btrfs\n"
"filesystem.",
NULL
},
@@ -171,12 +171,12 @@
},
{ do_ino_to_path, -2,
"inspect-internal inode-resolve", "[-v] <inode> <path>\n"
- "get file system paths for the given inode.\n",
+ "Get file system paths for the given inode.\n",
NULL
},
{ do_logical_to_ino, -2,
"inspect-internal logical-resolve", "[-v] [-P] <logical> <path>\n"
- "get file system paths for the given logical address.\n",
+ "Get file system paths for the given logical address.\n",
NULL
},
{ 0, 0, 0, 0 }
[-- Attachment #3: btrfsnewline.diff --]
[-- Type: text/x-patch, Size: 677 bytes --]
--- btrfs-progs/btrfs.c 2012-04-19 15:34:20.188146191 -0600
+++ btrfs.c 2012-04-19 15:40:43.681136087 -0600
@@ -95,7 +95,7 @@
"-t size minimal size of file to be considered for defragmenting\n"
},
{ do_get_default_subvol, 1, "subvolume get-default", "<path>\n"
- "get the default subvolume of a filesystem."
+ "get the default subvolume of a filesystem.\n"
},
{ do_fssync, 1,
"filesystem sync", "<path>\n"
@@ -171,7 +171,7 @@
},
{ do_ino_to_path, -2,
"inspect-internal inode-resolve", "[-v] <inode> <path>\n"
- "get file system paths for the given inode.",
+ "get file system paths for the given inode.\n",
NULL
},
{ do_logical_to_ino, -2,
next reply other threads:[~2012-04-19 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 22:26 James Daniel Smith [this message]
[not found] <1993875.Fsvh6l0u6C@linux-lt2.site>
2012-04-20 1:42 ` btrfs-progs James Daniel Smith
-- strict thread matches above, loose matches on Subject: below --
2011-11-01 16:34 btrfs-progs Andrew Benton
2011-11-02 14:45 ` btrfs-progs Leonidas Spyropoulos
2011-08-27 23:29 btrfs-progs Andrew Benton
2011-08-28 12:54 ` btrfs-progs Hugo Mills
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=14055805.ZYpkv1DjiU@linux-lt2.site \
--to=smithjd15@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;
as well as URLs for NNTP newsgroup(s).