If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: dietrich, Assigned: aravind)

Tracking

Details

(Reporter)

Description

8 years ago
we managed to hork the places branch somehow. can you nuke it and replace with a fresh m-c pull? (or let me know how, if i can do that from the client?)

we've only used it for test landings and perf testing so far, so the changeset history does not matter.
IT does the repo reset. RelEng may need to reconfig the master to fix the HgPoller.
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → mrz

Updated

8 years ago
Assignee: server-ops → mrz

Updated

8 years ago
Assignee: mrz → aravind
(Assignee)

Comment 2

8 years ago
Can this be done at any time?
(Reporter)

Comment 3

8 years ago
yep
(Assignee)

Comment 4

8 years ago
I wiped away the existing repo and cloned a new one from mozilla-central.  Please let me know if you need me to make any other changes to the repo.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.