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

Tags (such as "Reviewed-by") added to the downloaded mbox have no preceding empty line

Open
#400 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the issue by downloading a reviewed patch as an mbox from the Patchwork glibc project, then trace the mbox-download path that formats the commit message and Reviewed-by tag. Done means the generated mbox includes an empty line between the commit message text and the tag, matching the expected example.

Written by the indexing model from the issue text.

Description

I just used a v2.2.2 instance of patchwork (at https://patchwork.sourceware.org/project/glibc) to download a reviewed patch as an mbox. The downloaded patch had the reviewed-by line but it didn't have a blank line before it. For example, what I expected is:

Some text from the commit message. Then
some more text from the commit message.

Reviewed-by: Reviewer Name <foo@bar.com>

What I actually got was:

Some text from the commit message. Then
some more text from the commit message.
Reviewed-by: Reviewer Name <foo@bar.com>
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.