Page MenuHomeFreeBSD

getpatch: Do not error out if a patch has a custom encoding.
ClosedPublic

Authored by rakuco on Jul 13 2014, 12:05 PM.
Tags
None
Referenced Files
Unknown Object (File)
May 2 2024, 11:06 PM
Unknown Object (File)
May 2 2024, 9:24 PM
Unknown Object (File)
May 2 2024, 9:19 PM
Unknown Object (File)
Apr 17 2024, 6:02 AM
Unknown Object (File)
Apr 17 2024, 5:03 AM
Unknown Object (File)
Mar 17 2024, 12:29 AM
Unknown Object (File)
Mar 16 2024, 11:53 PM
Unknown Object (File)
Dec 22 2023, 10:11 AM
Subscribers
None

Details

Reviewers
sbz
Summary

Some patches, such as one of the ones sent in 189248, has a custom encoding, so the details page says "foo.diff (text/plain; charset=windows-1250)" instead of just "foo.diff (text/plain)". This made _extract_patchs_name() fail without any further explanation.

Make the regexp more flexible by accepting a charset entry after the mime-type in the details.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

rakuco retitled this revision from to getpatch: Do not error out if a patch has a custom encoding..
rakuco updated this object.
rakuco edited the test plan for this revision. (Show Details)
rakuco added a reviewer: sbz.
Tools/scripts/getpatch
123

Another possibility is matching \(text/plain instead of \(text/plain\) to accept anything coming after that.

sbz edited edge metadata.

Committed in r362667 . Thanks!

This revision is now accepted and ready to land.Jul 23 2014, 12:18 PM