marko10_000
/
btrfs-progs
forked from Mirrors/btrfs-progs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

btrfs-progs: docs: fix typos in READMEs, INSTALL and CHANGES 

Generated by https://github.com/jsoref/spelling

Issue: #154
Author: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: David Sterba <dsterba@suse.com>
master
Josh Soref 2018-11-26 17:47:22 +01:00 committed by David Sterba
parent f0cdb2c9fb
commit 2e67bf0ed6
5 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CHANGES
View File

@ -22,7 +22,7 @@ btrfs-progs-4.17.1 (2018-08-06)
* beautify progress output * beautify progress output
* btrfstune: allow to continue uuid change after unclean interruption * btrfstune: allow to continue uuid change after unclean interruption
* several fuzz fixes: * several fuzz fixes:
* detect overalpping chunks * detect overlapping chunks
* chunk loading error handling * chunk loading error handling
* don't crash with unexpected root refs to extents * don't crash with unexpected root refs to extents
* relax option parsing again to allow mixing options and non-options * relax option parsing again to allow mixing options and non-options
@ -181,7 +181,7 @@ btrfs-progs-4.13 (2017-09-08)
* check: new option --force to allow check of a mounted filesystem (no repair) * check: new option --force to allow check of a mounted filesystem (no repair)
* mkfs: --rootdir will now copy special files * mkfs: --rootdir will now copy special files
* dump-tree: minor output changes * dump-tree: minor output changes
* inspect rootid: accept file as arugment * inspect rootid: accept file as argument
* dev usage: don't calculate slack space for missing devices * dev usage: don't calculate slack space for missing devices
* fi du: don't print error on EMPTY_SUBVOL (inode number 2) * fi du: don't print error on EMPTY_SUBVOL (inode number 2)
* build: * build:
@ -244,7 +244,7 @@ btrfs-progs-4.11 (2017-05-18)
btrfs-progs-4.10.2 (2017-03-31) btrfs-progs-4.10.2 (2017-03-31)
* check: lowmem mode fix for false alert about lost backrefs * check: lowmem mode fix for false alert about lost backrefs
* convert: minor bugfix * convert: minor bugfix
* library: fix build, misisng symbols, added tests * library: fix build, missing symbols, added tests
btrfs-progs-4.10.1 (2017-03-17) btrfs-progs-4.10.1 (2017-03-17)
* receive: handle subvolume in path clone * receive: handle subvolume in path clone
@ -355,7 +355,7 @@ btrfs-progs-4.8.3 (2016-11-11)
btrfs-progs-4.8.2 (2016-10-26) btrfs-progs-4.8.2 (2016-10-26)
* convert: also convert file attributes * convert: also convert file attributes
* convert: fix wrong tree block alignment for unalianged block group * convert: fix wrong tree block alignment for unaligned block group
* check: quota verify fixes, handle reloc tree * check: quota verify fixes, handle reloc tree
* build: add stub for FIEMAP_EXTENT_SHARED, compiles on ancient kernels * build: add stub for FIEMAP_EXTENT_SHARED, compiles on ancient kernels
* build: add stub for BUILD_ASSERT when ioctl.h is included * build: add stub for BUILD_ASSERT when ioctl.h is included
@ -630,7 +630,7 @@ btrfs-progs-4.3 (2015-11-06)
* test for broken 'subvolume sync' * test for broken 'subvolume sync'
* basic tests for mkfs, raid option combinations * basic tests for mkfs, raid option combinations
* basic tests for fuzzed images (check) * basic tests for fuzzed images (check)
* command intrumentation (eg valgrind) * command instrumentation (eg valgrind)
* print commands if requested * print commands if requested
* add README for tests * add README for tests

2
INSTALL
View File

@ -62,7 +62,7 @@ documented in the Makefile.
The build utilizes autotools, dependencies for generating the configure The build utilizes autotools, dependencies for generating the configure
scripts are: scripts are:
* autconf, autoheader * autoconf, autoheader
* automake, aclocal * automake, aclocal
* pkg-config * pkg-config

2
README.md
View File

@ -85,7 +85,7 @@ Documentation updates
--------------------- ---------------------
Documentation fixes or updates do not need much explanation so sticking to the Documentation fixes or updates do not need much explanation so sticking to the
code rules in the previous section is not necessary. Github pull requests are code rules in the previous section is not necessary. GitHub pull requests are
OK, patches could be sent to me directly and not required to be also in the OK, patches could be sent to me directly and not required to be also in the
mailinglist. Pointing out typos via IRC also works, although might get mailinglist. Pointing out typos via IRC also works, although might get
accidentally lost in the noise. accidentally lost in the noise.

2
libbtrfsutil/README.md
View File

@ -452,7 +452,7 @@ A few guidelines:
* Don't require the Btrfs UAPI headers for any interfaces (e.g., instead of * Don't require the Btrfs UAPI headers for any interfaces (e.g., instead of
directly exposing a type from `linux/btrfs_tree.h`, abstract it away in a directly exposing a type from `linux/btrfs_tree.h`, abstract it away in a
type specific to `libbtrfsutil`) type specific to `libbtrfsutil`)
* Preserve API and ABI compatability at all times (i.e., we don't want to bump * Preserve API and ABI compatibility at all times (i.e., we don't want to bump
the library major version if we don't have to) the library major version if we don't have to)
* Include Python bindings for all interfaces * Include Python bindings for all interfaces
* Write tests for all interfaces * Write tests for all interfaces

6
tests/README.md
View File

@ -170,7 +170,7 @@ how to do mkfs, mount, unmount, check, loop device management etc.
and join by dashes `-`. This will become the directory name, eg. `012-subvolume-sync-must-wait`. and join by dashes `-`. This will become the directory name, eg. `012-subvolume-sync-must-wait`.
3. Write a short description of the bug and how it's tested to the comment at the 3. Write a short description of the bug and how it's tested to the comment at the
begining of `test.sh`. You don't need to add the file to git yet. Don't forget beginning of `test.sh`. You don't need to add the file to git yet. Don't forget
to make the file executable, otherwise it's not going to be executed by the to make the file executable, otherwise it's not going to be executed by the
infrastructure. infrastructure.
@ -194,7 +194,7 @@ $ TEST=012\* ./misc-tests.sh # from tests/
Most tests should be able to create the test images from scratch, using regular Most tests should be able to create the test images from scratch, using regular
commands and file operation. The commands also document the testcase and use commands and file operation. The commands also document the testcase and use
the teste code and kernel of the environment. the test code and kernel of the environment.
In other cases, a pre-created image may be the right way if the above does not In other cases, a pre-created image may be the right way if the above does not
work (eg. comparing output, requesting an exact layout or some intermediate work (eg. comparing output, requesting an exact layout or some intermediate
@ -244,7 +244,7 @@ There are some utilities that are not distributed but are necessary for the
tests. They are in the top level directory of the testsuite and their path tests. They are in the top level directory of the testsuite and their path
cannot be set. cannot be set.
The tests assume write acesss to their directories. The tests assume write access to their directories.
# Coding style, best practices # Coding style, best practices