vitalif
/
e2fsprogs
mirror of https://github.com/vitalif/e2fsprogs
1
0
Fork 0
Code Issues Releases Wiki Activity

Fix documentation: BLOCK_FLAG_TRAVERSE should be BLOCK_FLAG_DEPTH_TRAVERSE 

Addresses Debian Bug #351268

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
bitmap-optimize
Theodore Ts'o 2006-03-18 08:26:36 -05:00
parent cbb7f9c4f1
commit 7447921dff
4 changed files with 15 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/ChangeLog
View File

@ -1,3 +1,9 @@
2006-03-18 Theodore Ts'o <tytso@mit.edu>
* libext2fs.texinfo (Iterating over blocks in an inode): Fix
BLOCK_FLAG_TRAVERSE so it is the correct
BLOCK_FLAG_DEPTH_TRAVERSE. (Addresses Debian Bug #351268)
2006-06-30 Theodore Ts'o <tytso@mit.edu>
* Release of E2fsprogs 1.38

2
doc/libext2fs.texinfo
View File

@ -516,7 +516,7 @@ blocks where the block number is zero (also known as ``holes''.) It is
also known as BLOCK_FLAG_APPEND, since it is also used by functions
such as ext2fs_expand_dir() to add a new block to an inode.
@item BLOCK_FLAG_TRAVERSE
@item BLOCK_FLAG_DEPTH_TRAVERSE
This flag indicates that the iterator function for the
indirect, doubly indirect, etc. blocks should be called after all
of the blocks containined in the indirect blocks are processed.

5
lib/ext2fs/ChangeLog
View File

@ -1,3 +1,8 @@
2006-03-18 Theodore Ts'o <tytso@mit.edu>
* ext2fs.h: Fix documentation so that BLOCK_FLAG_TRAVERSE is
BLOCK_FLAG_DEPTH_TRAVERSE. (Addresses Debian Bug #351268)
2006-03-17 Theodore Ts'o <tytso@mit.edu>
* initialize.c (calc_reserved_gdt_blocks): Fix a signed vs

6
lib/ext2fs/ext2fs.h
View File

@ -269,9 +269,9 @@ struct struct_ext2_filsys {
* to an inode. It can also be used for programs that want to be able
* to deal with files that contain "holes".
*
* BLOCK_FLAG_TRAVERSE indicates that the iterator function for the
* indirect, doubly indirect, etc. blocks should be called after all
* of the blocks containined in the indirect blocks are processed.
* BLOCK_FLAG_DEPTH_TRAVERSE indicates that the iterator function for
* the indirect, doubly indirect, etc. blocks should be called after
* all of the blocks containined in the indirect blocks are processed.
* This is useful if you are going to be deallocating blocks from an
* inode.
*