Deal with spaces in patch descriptions
commitcf17be6d97df34e993c8c1ab07f74ce1a8574714
authorH.Merijn Brand - Tux <h.m.brand@xs4all.nl>
Sun, 10 Feb 2013 19:45:29 +0000 (10 20:45 +0100)
committerH.Merijn Brand - Tux <h.m.brand@xs4all.nl>
Sun, 10 Feb 2013 19:45:29 +0000 (10 20:45 +0100)
tree123aa12e60fde5639103d9e48f76f860cbb86a94
parent67269d3ce489a8484197a38cd148b7b85905c307
Deal with spaces in patch descriptions

To be sure, I also allowed "Compile time options" to have spaces
Using \0 as a new separator seems a sane choice, as the values returned
from internal functions are pure C strings, so they end with \0

patches can have spaces:
#          $got->{build}{patches}[0] = 'SAVEARGV0'
#     $expected->{build}{patches}[0] = 'SAVEARGV0 - disable magic open in <ARGV>'
#          $got->{build}{patches}[0] = 'ActivePerl'
#     $expected->{build}{patches}[0] = 'ActivePerl Build 1602 [296513]'
#          $got->{build}{patches}[0] = 'DEBPKG:debian/arm_thread_stress_timeout'
#     $expected->{build}{patches}[0] = 'DEBPKG:debian/arm_thread_stress_timeout - http://bugs.debian.org/501970 Raise the timeout of ext/threads/shared/t/stress.t to accommodate slower build hosts'
#          $got->{build}{patches}[0] = 'Bug#55162'
#     $expected->{build}{patches}[0] = 'Bug#55162 File::Spec::case_tolerant performance'
Changelog
V.pm