+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
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.
+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
* 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.
*