On Thu, Aug 31, 2017 at 08:43:21AM -0400, Brian Foster wrote: > FWIW, I don't really have a strong opinion. To me, removing experimental > means we feel the code has stabilized long enough in principle, there > are no significant problems (i.e., corruption/crash vectors) that we are > aware of and the feature is complete (full userspace tool support, etc). > The in-core extent list thing seems like more of a general problem to me Agreed so far. > That aside, shouldn't we consider the rmapbt experimental tag first, or > at least at the same time? It's been around for slightly longer. I've not done much testing on that or have experience with it in general, nor do I have a customer with a big QA team beating it hard, so I can't really comment on that one. -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
