https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244389
Phil Shafer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Phil Shafer <[email protected]> --- Yes, this is completely broken in a conceptual way. The tags in libxo should be thought of as "columns" in a database, not as data. Using a pid as the tag here is wrong; it should be more like: ... <binary> <process> <pid>48700</pid> <command>zsh</command> ... The big question is: how do we manage changes to libxo-based encoding? If we make this change (or other future changes), then there is a risk of breaking something that depends on it? How do we announce changes that are not backwards compatible? Do we just declare is a "bug" that we fix and announce via release notes? Do we need to start using xo_version() calls? Do we enforce the use of xo_version at the first change? How do we arrive on a policy that we are all comfortable with? In this case, it's a obvious bug in XML, but folks using JSON might be depending on it, so it's a semi-perfect example. Thanks, Phil -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
