* Noteworthy changes in release ?.? (????-??-??) [?]
+** New features
+
+ parted has improved support for partitionable loopback devices
+
+** Bug fixes
+
+ parted now exits nonzero for certain failures already diagnosed as "Error".
+ For example, before this change, parted would exit successfully in spite
+ of "Error: ...unrecognised disk label" and "Error:... both GPT primary
+ and backup partition tables are corrupted".
+
+ libparted: gpt_disk_duplicate now copies the flags over to the new
+ disk object. Previously the flags would be undefined.
+
+ libparted can now read partition tables with a number of partition
+ array entries that is different from the default of 128. Before,
+ it would fail to recognize them and could even read beyond the end
+ of a heap-allocated buffer.
+
+ libparted: no longer aborts (failed assertion) due to a nilfs2_probe bug
+ [bug introduced in parted-2.4 with the addition of nilfs2 support]
+
+ libparted: no longer aborts when reading a truncated GPT-formatted device
+ [bug present at least as far back as RHEL4's parted-1.6.19]
+
+ libparted: works with a two-component linux kernel version number like 3.0
+ [bug present since the beginning]
+
+ libparted: strengthen the pc98 test so that it is much less likely to
+ cause an MSDOS partition table to be mistakenly identified as pc98.
+ [bug present since the beginning]
+
+ libparted no longer gets a failed assertion when probing a partition
+ with an HFS or HFS+ signature, but with invalid ->total_blocks and/or
+ ->block_size values.
+
+** Changes in behavior
+
+ parted: mkpart command has changed semantics with regard to specifying end
+ of the partition. If the end is specified using MiB, GiB, etc. unit, parted
+ subtracts one sector from the specified value. With this change, it is now
+ possible to create partitions like 1MiB-2MiB, 2MiB-3MiB and so on.
+
+** Build-related
+
+ "make dist" no longer builds .tar.gz files.
+ xz is portable enough and in wide-enough use that distributing
+ only .tar.xz files is enough.
+
+
+* Noteworthy changes in release 3.0 (2011-05-30) [stable]
+
** Bug fixes
+ Fix numerous small leaks in both the library and the UI.
+
+** Changes in behavior
+
+ Remove all FS-related (file system-related) sub-commands; these commands
+ are no longer recognized because they were all dependent on parted "knowing"
+ too much about file system: mkpartfs, mkfs, cp, move, check, resize.
+ This change removes not just the user interface bits, but also the
+ library functions and nearly all of the underlying FS-munging code.
+ The code embedded in Parted by which it knew about those file systems
+ was so old, unmaintainable and buggy that while seemingly drastic,
+ this change is like removing a gangrenous toe.
+
+ Here is the list of removed functions:
+
+ ped_file_system_clobber
+ ped_file_system_open
+ ped_file_system_create
+ ped_file_system_close
+ ped_file_system_check
+ ped_file_system_copy
+ ped_file_system_resize
+ ped_file_system_get_create_constraint
+ ped_file_system_get_resize_constraint
+ ped_file_system_get_copy_constraint
+
+ This change also removes the corresponding function members
+ from "struct _PedFileSystemOps":
+
+ clobber open create close check copy resize get_create_constraint
+ get_resize_constraint get_copy_constraint
+
+
+* Noteworthy changes in release 2.4 (2011-05-18) [stable]
+
+** Bug fixes
+
+ parted no longer allows the modification of certain in-use partitions.
+ In particular, before this fix, parted would permit removal or modification
+ of any in-use partition on a dmraid and any in-use partition beyond the 15th
+ on a regular scsi disk.
+
Improve support of DASD devices on the s390 architecture.
Parted now supports all DASD types (CKD and FBA), DASD formats (CDL,
LDL, CMS non-reserved, and CMS reserved), and DASD drivers (ECKD, FBA,
"parted $dev print" now prints information about the device (model, size,
transport, sector size) even when it fails to recognize the disk label.
+ specifying partition start or end values using MiB, GiB, etc. suffixes
+ now makes parted do what I want, i.e., use that precise value, and not
+ some other that is up to 500KiB or 500MiB away from what I specified.
+ Before, to get that behavior, you would have had to use carefully chosen
+ values with units of bytes ("B") or sectors ("s") to obtain the same
+ result, and with sectors, your usage would not be portable between devices
+ with varying sector sizes. This change does not affect how parted handles
+ suffixes like KB, MB, GB, etc.
+
* Noteworthy changes in release 2.3 (2010-05-28) [stable]