On 3/1/24 00:37, Oliver Webb via Toybox wrote: > Heya, Was trying to not bother the list on Feb 29th because 0.9 (0.8.11?) was > supposed to come out,
I didn't manage it. I wound up tangenting through optarg.c instead, and I still haven't done a proper lib/passwd.c test setup (the new infrastructure caused regressions, I un-promoted a command I really want to promote again), and so on. Going through the git log to assemble release notes tends to find loose ends... Also I'm packing so I can sell my house and move (my wife got her doctorate so she's probably moving for a job, dunno where yet). I was trying to get out a release _before_ the storage pod arrived and box wrangling became more urgent. (The old "important vs urgent" scale...) > And I didn't wanna delay it with things like bc cleanup. ... > This patch removes a lot of stuff, and is therefore way too large to get > through the spam filter in it's plain form. > Since if It gets caught in it no one on the list can see it besides rob. I've > compressed the patch with gzip -9. > (Only people that can decompress the patch seeing it is better then _noone_ > being able to unless it gets applied). > I've never delt with a patch this large, and it cant be broken up easily > (parse.txt cleanup is 90% of it), so this seemed > like the best solution. The patch is about 180k uncompressed Applied. In theory git has extended patch formats that can rename files, and I _think_ can also delete them without saying what the old contents was, but alas the documentation is terrible and "git format-patch" does not by default PRODUCE the stuff that "git am" can understand. (You need to add -M for the move ones, and even then it didn't do it reliably for me and I wound up editing them by hand...) Rob _______________________________________________ Toybox mailing list [email protected] http://lists.landley.net/listinfo.cgi/toybox-landley.net
