No way to ask Launchpad to refresh a stale diff

Bug #483945 reported by Jonathan Lange on 2009-11-17
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Colin Watson

Bug Description

The diff on a merge proposal can be stale, especially when the target branch has changed but the source branch hasn't. In these cases, there's no way of asking Launchpad to regenerate the diff. Perhaps there should be.

WORK AROUND
Ask a webops on #launchpad-dev or #launchpad-ops to unscan the proposed branch.

Related branches

Tim Penhey (thumper) on 2009-11-27
Changed in launchpad-code:
importance: Undecided → Low
status: New → Triaged
Monty Taylor (mordred) on 2010-08-19
tags: added: openstack
Tim Penhey (thumper) on 2010-08-19
tags: added: trivial
Martin Pool (mbp) on 2011-07-27
tags: added: mp-preview-diff
Curtis Hovey (sinzui) on 2012-11-28
description: updated
Colin Watson (cjwatson) on 2017-11-24
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Colin Watson (cjwatson)
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Colin Watson (cjwatson) on 2017-11-27
tags: added: qa-ok
removed: qa-needstesting
description: updated
Colin Watson (cjwatson) wrote :
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers