I think if a user inputs +9.5GB for the end sector, it would be slightly confusing to silently drop the .5GB and just provide 9GB. I understand this is a limitation of GPT fdisk only allowing integers.
Could we maybe convert 9.5G to 9500MB to allow decimals in GB?
I'd imagine this decimal trickery would only be available for GB, TB, PT, and not MB.
Thanks,
-Mitch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That sort of conversion is certainly possible, but would add code complexity that I'd prefer to avoid. That said, I'm willing to consider a patch/merge request; but at the moment I'm pretty busy with other matters, so I don't have much time to devote to this issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, Regarding the change to allow decimal formatting https://sourceforge.net/p/gptfdisk/code/ci/e1cc654ef71996d836c5d051278130f50f768f84
I think if a user inputs +9.5GB for the end sector, it would be slightly confusing to silently drop the .5GB and just provide 9GB. I understand this is a limitation of GPT fdisk only allowing integers.
Could we maybe convert 9.5G to 9500MB to allow decimals in GB?
I'd imagine this decimal trickery would only be available for GB, TB, PT, and not MB.
Thanks,
-Mitch
That sort of conversion is certainly possible, but would add code complexity that I'd prefer to avoid. That said, I'm willing to consider a patch/merge request; but at the moment I'm pretty busy with other matters, so I don't have much time to devote to this issue.