Closed Bug 761669 Opened 12 years ago Closed 5 years ago

[shipping] collapse changesets that have been pushed before, in particular on migration

Categories

(Webtools Graveyard :: Elmo, defect, P3)

Product:
Webtools Graveyard
Component:
Elmo
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: Pike, Unassigned)

References

Details

When migrating from aurora to beta, there's often a "merge fx10 to beta" changeset, that's nothing but the zero-op merge of what's already on aurora. Now that we show the pushes on aurora, we should collapse the changesets that we already have in the view.

There's a trick here in that we may only see a single push on aurora, but that's signaling all the 28 pushes that get merged over and their changesets. So there might be a need to check parents or so.

Probably better to fix once we have the class-based view and got rid of rowcollector, bug 761662.
Priority: -- → P3

This has gone away with cross-channel.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.