Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

git am cannot parse the mbox when PGP signatures are present

Open
#221 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Reproduce the problem using the attached orig.mbox.gz and the Patchwork mbox URL, then trace the code that reformats messages containing PGP signatures and preserves the Content-Type header. Done means the generated mbox no longer claims to be multipart/signed after MIME and signature removal, and git am can parse it.

Written by the indexing model from the issue text.

Description

bug

Here is an example from the kernel mailing list:

https://patchwork.kernel.org/patch/10656215/mbox/

The original mbox is attached to this issue.

Patchwork removed all the MIME encoding and signature but retained the Content-Type header saying it is in multipart/signed format.

'git am' knows how to parse this header and gets confused when the mailbox is no longer in the right format.

patchworks should also drop the content-type header if it is going to do this kind of reformatting.

orig.mbox.gz

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.