Showing a diff between two versions of the same series

Open
#636 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, python

Research direction

Start by reviewing the referenced Patchew diff module and series-diff.html template, then inspect how Patchwork identifies series and message IDs. Done means users can view a diff between two submitted series versions, initially using two message IDs if version tracking is not implemented.

Written by the indexing model from the issue text.

Description

Hello,

First, thank you for developing and maintaining this great tool!

For the MPTCP project, we are also using Patchew, mainly to apply patches in a Git repo, but also for extra features like showing a diff between two versions of the same series. Example: when looking at a series on Patchew, you can see at the top "Diff against v1 v2 v3"

Showing the diff between versions only need access to the patches, no need to apply them in a repo. Here is what Patchew is doing with the help of jsdifflib: diff module & diff template. Ideally, patchwork would need the ability to track series' versions (which would be great for the reviewers to quickly jump between versions), but this can also be optional: the first version could start with only showing a diff between two series' message-ids given by the user for example.

(Note that having Patchwork being able to directly apply patches in a repo would be great, not depends on another service regularly polling for new events, but that's another topic :) )

Dominant language
Python
Stars
317
Forks
91
PR merge metrics
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.