On 4/29/18 11:45 AM, Eric Sandeen wrote: >> Assuming that the plan is to leave it enabled in F-29 on branching and >> have it ship enabled in F-29 I agree, if the intention is to leave it >> enabled in rawhide and disable it on branching then the Change >> Proposal mechanism isn't the way to ensure wider knowledge. > I'd be happy to have it left on for F29, it /might/ even be default upstream > by the time F29 ships. I'll need to re-familiarize myself w/ the > "System-Wide Change Proposal" process, I guess. > > FWIW, turning it on has very little effect until it's actually used, so it > really should not be destabilizing for most, even if bugs lurk. ;) > > -Eric Getting back on topic (back from the Shrink Wars), I'd like to get this turned on. I'd prefer to do this via a soon-to-land patch which enables config files for mkfs, so that distros can set their own defaults without having to patch source. I'm going to give it a bit of time to see if we can get that upstream, and then will see about simply shipping that patch along w/ a config file that enables reflink for F29. Thanks, -Eric _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
