Resubmit should generate interdiffs

Bug #400439 reported by Aaron Bentley
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

When resubmit is used, we should generate an interdiff. It should be attached to the initial email, and it should be shown in the page. It should show only changes originated in the branch, not changes that were merged in.

Tags: lp-code
Tim Penhey (thumper)
Changed in launchpad-code:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Robert Collins (lifeless) wrote :

I'm not clear what would be interdiffed here. Also is it meaningfully different to the use of your clever diff plugin on incremental commits?

Changed in launchpad:
status: Triaged → Incomplete
Revision history for this message
Aaron Bentley (abentley) wrote :

By "Interdiff", I meant a diff showing only the changes made on the mainline after the review, so that it is easy for the reviewer to see what changes were made to address their review.

A "bzr diff -r $REVIEWED_REV..-1" would suit the purpose except that it would also include changes merged in from the target branch.

This is somewhat addressed by the post-comment revision diffs we now include, but those will show merges from the target. They also take a long time to appear, once requested.

Revision history for this message
Aaron Bentley (abentley) wrote :

And they aren't put into emails at all.

Changed in launchpad:
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.