Third: Implementation of "raw" functionality to reply to a subset of patches from a series. It is "raw" in the sense that it doesn't implement a way to toggle the reply to all patches (which was the previous behavior) and doesn't update the UI component for this functionality
Fourth: Implement the key bind uppercase R to toggle the reply to all patches
Fifth: Update the UI to reflect the changes introduced by the third and fourth commits
One can argue that the last three should be squashed as they can be seen as atomic, in the sense that a "stable" version would also include the previous behavior along with the UI. However, I chose to split those to keep the commits more readable and understandable in chunks. Of course, this makes commits 3 and 4 somewhat "unstable", but we can always opt to squash those before merging...
Closes: #78
Showcase
Selecting patches 0 and 5 from a series with 29 patches
PR Commits
Rto toggle the reply to all patchesOne can argue that the last three should be squashed as they can be seen as atomic, in the sense that a "stable" version would also include the previous behavior along with the UI. However, I chose to split those to keep the commits more readable and understandable in chunks. Of course, this makes commits 3 and 4 somewhat "unstable", but we can always opt to squash those before merging...
Closes: #78
Showcase
Selecting patches 0 and 5 from a series with 29 patches
Selecting patch 1 of a series with only one patch
Selecting a patch that has already been reviewed