move all todo entries to a later date that do aren't really urgent bugs
svn path=/trunk/extragear/sysadmin/partitionmanager/; revision=1236311
This commit is contained in:
parent
9eb62abf1f
commit
776c19da03
12
TODO
12
TODO
|
@ -9,11 +9,15 @@ Bugs to fix for 1.1:
|
|||
if the new one is not legal. i.e., we must constantly update the valid ranges
|
||||
of the spin boxes if any value changes.
|
||||
|
||||
* how does one remove an existing mount point?
|
||||
|
||||
* how do we know the first usable sector for GPT when default is not aligned
|
||||
and we've just created the new partitiontable op?
|
||||
|
||||
===============================================================================
|
||||
|
||||
For releases after 1.1:
|
||||
|
||||
* add a way for the user to remove an existing mount point
|
||||
|
||||
* make Job::copyBlocks() work for cases where the logical sector sizes of
|
||||
source and target are not the same
|
||||
|
||||
|
@ -21,10 +25,6 @@ Bugs to fix for 1.1:
|
|||
configuration? would we need to know the physical sector size for that? are
|
||||
we able to acquire that information?
|
||||
|
||||
===============================================================================
|
||||
|
||||
For releases after 1.1:
|
||||
|
||||
* find an elegant solution for the brokenness in design that is
|
||||
Partition::sectorSize()... Either a Partition has a reference/pointer to the
|
||||
Device it's on or the method is removed completely. -- Maybe the
|
||||
|
|
Loading…
Reference in New Issue