On 02/23/2016 05:52 PM, John Snow wrote: > "Couldn't determine the cluster size of the target image, which has no > backing file" is more correct. The problem is not why we couldn't > determine it, but instead that we were unable to AND there is no backing > file, so our inability to determine it is a problem. > > What's our policy on error message strings that eclipse 80 columns? I > was told once (at gunpoint; I live in the USA) to never split up long > strings because it makes them harder to grep for.
I don't mind error messages longer than 80 columns; and I also don't mind string concatenation to fit the source of the message into reasonable lengths (when I grep for a message, I just grep for the first few words, not the whole message, precisely so that line wraps later in the message don't cause me grief). There's varying opinions from other contributors on whether an error message can be split, but I don't see anything in HACKING that says which style must prevail. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
