Launchpad itself

merge proposal not shown for branch

Bug #640810 reported by Jelmer Vernooij on 2010-09-16

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Triaged	Low	Unassigned

Bug Description

https://code.edge.launchpad.net/~jelmer/launchpad/635591-sync-source-unicode has two merge proposals associated with it. However, only the last one is shown.

The merge proposals are:
https://code.edge.launchpad.net/~jelmer/launchpad/635591-sync-source-unicode/+merge/35637 (not shown)
https://code.edge.launchpad.net/~jelmer/launchpad/635591-sync-source-unicode/+merge/35715 (shown)

Tags:

Revision history for this message

Tim Penhey (thumper) wrote on 2010-09-16:

This is by design. Old merges for a project can be traversed to through the +merges view of the project.

Changed in launchpad-code:
status:	New → Incomplete

Revision history for this message

Robert Collins (lifeless) wrote on 2011-01-12:

Why not show them for the branch? +merges seems rather indirect. I think a little expander that makes an api call would be tasteful and not impact common case performance. Marking low though as its polish not immediately in our roadmap.

Changed in launchpad:
status:	Incomplete → Triaged
importance:	Undecided → Low

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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