Should BUG= lines be able to span multiple lines and still be effective (e.g., at updating the appropriate bugs when they are committed)? For instance, this CL:

https://chromium-review.googlesource.com/#/c/397003/

has this:

BUG=chrome-os-partner:58609, chrome-os-partner:59197,
    chrome-os-partner:57928, chrome-os-partner:57445

but only the first two bugs got updated when the CL landed. I've seen a handful of other CLs that affect many bugs like this.

This creates a bit of confusion, because our pre-upload checks complain about commit messages with lines that are longer than ~70-80 characters, so some developers accordingly wrap these lines.

I can't figure out where the BUG= processing happens; is this a GoB plugin? Is it reasonable to try to handle multi-line messages like this? Or maybe we should just have multiple BUG= lines, like this?

BUG=chrome-os-partner:58609, chrome-os-partner:59197
BUG=chrome-os-partner:57928, chrome-os-partner:57445