On Sun, Feb 03, 2019 at 08:50:48AM +0100, Chris Lamb wrote: > Chris Lamb wrote: > > > > I'll dig in a bit more and see if I can fix libeatmydata, but it might > > > end up being too invasive and time consuming. I'll send another message > > > once I know more. > > > > Oh, nice analysis so far. Sounds like that needs to get (at least > > copied...) upstream at the very least so that it doesn't > > accidentally lost in this "branch" bug report. > > > > (Probably has implications for other packages that Santiago is > > testing too, naturally…) > > Any further thoughts folks? :)
Based on everything Alberto said, should this bug not be reassigned to eatmydata? Thanks.
