HI Sean, On Do 03 Aug 2017 17:06:19 CEST, Sean Whitton wrote:
Hello Russ, On Wed, Aug 02, 2017 at 11:54:52AM -0700, Russ Allbery wrote:I like solution (a), honestly. I think we could just add backslash as an escape character that escapes anything other than a newline and have the problem basically go away. It would require a new version of the spec, though, since it's not backward compatible (although I doubt many files contained literal backslashes).Okay.Line-based lists is much less backward-compatible, since we break every debian/copyright file that uses space-separated lists, which is much more common than having whitespace in filenames.My suggestion was that the Files: field could be /either/ a line-based list or a space-separated list -- is there something that would break?
How would differentiate between a blank in a file name and a blank as a separator?
Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgpIKKSW4ahJZ.pgp
Description: Digitale PGP-Signatur
