On Sat, Nov 14, 2020 at 11:42:25AM -0700, Curtis Gedak wrote: > On 2020-11-13 5:11 p.m., Brian C. Lane wrote: > > <snip> > > > > A big part of the trouble here was in the resize code, which we need to > > talk about. > > > > I'd like to get a 3.4 release with these patches out before the end of > > the year. Next year I want to drop the /r/ resize library again. It has > > no place in parted, isn't maintained, and isn't something I'd suggest > > anyone using. Filesystem code should be maintained by filesystem tools > > so if someone wants to move it into some other project that's fine with > > me but I strongly believe that it needs to be removed. > > > > We can talk about that in another thread though. For this one it would > > be good if people who care about the resize code make sure I didn't > > introduce new bugs. The tests pass, and we do have some for the resize > > code, but inside there is a twisty path that I'm sure isn't covered > > 100%. > > > > <snip> > > Can someone point me to an easy way to apply all of these patches? > > For example is there a git branch I can check out to compile and test? > > I would prefer not to have to save and apply each one of the 24 patches > just to be able to run some tests.
Whoops, I meant to add that to the cover letter: https://github.com/bcl/parted/tree/master-gcc10-warnings -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
