tinderboxpushlog should put markers next to non-default-branch changesets

VERIFIED FIXED

Status

--
major
VERIFIED FIXED
9 years ago
4 years ago

People

(Reporter: dbaron, Assigned: mstange)

Tracking

Details

Tinderboxpushlog should, like the pushlog does, put markers next to changesets that aren't on the default branch (showing what branch they're on) so that people don't get confused by relbranch changes in terms of figuring out when a regression happened.
Severity: normal → major
(Assignee)

Comment 1

9 years ago
http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/1a9a8162c435
http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/0f42dfadef52
Assignee: nobody → mstange
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
gozer, MoMe TBPL wants this.
V.Fixed, per Firefox3.5 'tbirdbld – Mon Jan 11 09:13:16 2010 PST' push.

Yet, it's not as noticeable as I would have hoped:
could it be possible to copy the branch tags from the newest changeset, or at least a hint, to the push line itself?
(Or anything that would not require to check the changeset comment manually?)
Status: RESOLVED → VERIFIED
(Assignee)

Comment 4

9 years ago
That's a good idea, please file a new bug for that.
(In reply to comment #4)

I filed bug 539347.
(In reply to comment #2)
> gozer, MoMe TBPL wants this.

Pulled in MoMe TBPL. Should be reflect live in the next hour or so
(In reply to comment #6)
> Pulled in MoMe TBPL.

V.Fixed too.

*****

NB: I noticed 'default' (and 'tip') are displayed too (now). Why not ;-)
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.