https://bugs.kde.org/show_bug.cgi?id=384321
Andrius Štikonas changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kpm |https://invent.kde.org/syst
https://bugs.kde.org/show_bug.cgi?id=384321
--- Comment #7 from Andrius Štikonas ---
Git commit d27455b6f08e42470f375de679b1751a4972d73b by Andrius Štikonas.
Committed on 04/12/2017 at 21:19.
Pushed by stikonas into branch 'sfdisk'.
Avoid unnecessary QString encoding/decoding.
M +1-1sr
https://bugs.kde.org/show_bug.cgi?id=384321
--- Comment #6 from Andrius Štikonas ---
Ok, thanks for explaining. Getting a bit clearer (I didn't have much
experience with this encoding stuff before.
I think KPM will never work on Windows or Mac OS. But better be safer now. In
any case I would li
https://bugs.kde.org/show_bug.cgi?id=384321
--- Comment #5 from Pali Rohár ---
Block device name is just ordinary file. In most cases people use only ascii
characters (because non-ascii names are lot of times broken in CLI or GUI
tools), but there is no restrictions for 8bit. On linux you can cal
https://bugs.kde.org/show_bug.cgi?id=384321
--- Comment #4 from Andrius Štikonas ---
(In reply to Pali Rohár from comment #3)
> > -if
> > (QFileInfo(QString::fromUtf8(storage.device())).canonicalFilePath() ==
> > canonicalDeviceNode ) {
> > +if
> > (QFileInfo(QString::fromLocal
https://bugs.kde.org/show_bug.cgi?id=384321
Pali Rohár changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=384321
--- Comment #2 from Andrius Štikonas ---
Git commit f09cb6435ec8ec6175d098b6bb5cb5bfb5871f54 by Andrius Štikonas.
Committed on 03/12/2017 at 12:40.
Pushed by stikonas into branch 'sfdisk'.
Fix conversion to/from QByteArray in sfdisk backend.
M +3
https://bugs.kde.org/show_bug.cgi?id=384321
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=384321
Andrius Štikonas changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
