From 5efcdf7a2bfafd01e5c6d53dd46335f30704b2ad Mon Sep 17 00:00:00 2001 From: Artem Bityutskiy Date: Fri, 18 Mar 2011 13:31:09 +0200 Subject: mkfs.ubifs: deprecate squash-rino-perm options As we have planned, make --nosquash-rino-perm option to be the default. Deprecate both options at the same time and print a warning if they are used. Later we can remove them Also, bump mkfs.ubifs version number. Signed-off-by: Artem Bityutskiy --- feature-removal-schedule.txt | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) (limited to 'feature-removal-schedule.txt') diff --git a/feature-removal-schedule.txt b/feature-removal-schedule.txt index 4e9824a..2899e34 100644 --- a/feature-removal-schedule.txt +++ b/feature-removal-schedule.txt @@ -13,19 +13,18 @@ a bug which was found too late, when mkfs.ubifs had already been used in production. To fix this bug, 2 new options were introduced: --squash-rino-perm which preserves the old behavior and --nosquash-rino-perm which makes mkfs.ubifs use the right permissions for the root -inode. For now --squash-rino-perm is the default, and if neither ---squash-rino-perm nor --nosquash-rino-perm are used, mkfs.ubifs prints a -warning. This was introduced in mtd-utils-1.4.0 (13 Sep 2010). - -So the plan is (to be done by Artem Bityutskiy): - -1. keep the warning for few releases to make sure users start using one of the - options. Update the mkfs.ubifs documentation at the web site. -2. make --nosquash-rino-perm to be the default, and remove the warning. - Update the mkfs.ubifs documentation at the web site. -3. eventually deprecate both options by: -3.1 adding a warning to make users stop using them -3.2 removing both options. +inode. + +For a while (releases 1.4.0-1.4.3) --squash-rino-perm was the default, and if +neither --squash-rino-perm nor --nosquash-rino-perm were used, +mkfs.ubifs printed a warning. This was introduced in mtd-utils-1.4.0 (13 Sep 2010). + +Now we have removed a warning and made --nosquash-rino-perm to be the +default. Also, both options are declared depricated, so users should try +to stop using them. + +The further step is to remove both of them. + --------------------------- 2. nanddump: fail when the -s parameter is not page aligned -- cgit v1.2.3