Bug merge more senders into single one

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

Nobody has claimed this yet.

Assessment

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

Research direction

Use the three linked Patchwork and lore.kernel.org messages as reproduction cases, starting by tracing how Patchwork extracts and groups sender identities. Done means the distinct senders are no longer merged incorrectly, while names such as “via ltp” are handled as described in the issue.

Written by the indexing model from the issue text.

Description

Here are 3 examples of different senders which are under cel--- via ltp user:

Some of them have somehow wrongly set git send-email, because the have in ML ... via ltp <ltp@lists.linux.it> (any hint, what is wrongly set?), but at least j.nixdorf@avm.de <j.nixdorf@avm.de> should have correct setup.

Also, it'd be great if patchwork could recognise different name in ... via ltp <ltp@lists.linux.it>.

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.