[MERGE] pybaz: sanitize patch logs for more tla quirks

[Robert Collins]

Hi, this patch turns a patch log like:

Revision: foo--0--patch-1
Archive: foo at example.com
Creator: Robert Collins <rbtcollins at hotmail.com>
Date: ...
Standard-date: ...
Summary: ...
Keywords:
Patches applied:
New-files: ...
New-directories: ...
Modified-files: ...
New-patches: ...

Message here

into

Revision: foo--0--patch-1
Archive: foo at example.com
Creator: Robert Collins <rbtcollins at hotmail.com>
Date: ...
Standard-date: ...
Summary: ...
Keywords:
Patches-applied:
New-files: ...
New-directories: ...
Modified-files: ...
New-patches: ...

Message here


(Note the 'Patches-applied:' line.) during log parsing. This allows
baz-import to import some branches where tla has incorrectly considered
user log message data as rfc2822 header data.

It shouldn't affect any existing imports, as this corruption would have
triggered an exception in all cases AFAICT.

No tests, as I figure ddaa will want to do that ;););).

That said, I think this is important to get into pybaz for debian and
for dapper, because I suspect this corruption may be the cause of a
number of reported import failures.

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060424/41cf1865/attachment.pgp