I took my time reading DEP3 (http://dep.debian.net/deps/dep3/) and notice they introduce an new "RFC-2822-like" format. This time they introduce an ambiguous rules where either the Description or the Subject field and contain verbatim data (which one is uncertain to me, the text implies one of them, but says Description first, and Subject later). This will off course require an specific parser as a parser for the debcontrol format can't be used due to this rule. Including this with the policy that only debian/control can contain comments (policy 5.2) and that DEP5 (http://dep.debian.net/deps/dep5/) introduces a "superset of RFC2822". Wouldn't it now be a good time to formally define a format that can be parsed with a generic parser, instead of continuing the invention of additional RFC-2822++ formats?
On an other note, the DEP3 verbatim data specifier doesn't define any limits on what data it can contain, so the content "...as you can see in the following\nbug: blablabla" is ambiguous as best. -- /Carl Fürstenberg <azat...@gmail.com> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
