George Dunlap writes ("Re: [PATCH for-4.11 0/2] SUPPORT.md matrix fixes (series
"C")"):
> Right, so there are four options:
>
> 1. Never rename / reorganize SUPPORT.md categories
This is clearly unworkable.
> 3. Introduce some sort of “mapping” of options so that the table
> generator can correctly construct rows
I think this would be quite annoying. It would have to be maintained
separately, probably in the branch for the next version. It would
also make the table generator more complicated and it's quite bad
enough already.
> 2. Backport all renames / reorganizations to all supported versions
> 4. Tolerate duplicate rows for renamed / reorganized features
So it has to be one of these. IMO either of these is fine.
> I was initially opposed to #2, but I think the idea is growing on
> me. It does mean SUPPORT.md may end up being reorganized or renamed
> in point releases, however. It’s a bit hard for me to tell how
> disruptive that would be.
We don't have to make this decision the same way for every feature.
If someone wants to send a patch (on top of my backport series,
please) that renames "PVH guest" to "PVH" in 4.10, and changes
"Status:" to "Status, domU:", to match 4.11 that would be fine by me.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
