Closed
Bug 573491
Opened 14 years ago
Closed 14 years ago
move hg.mozilla.org/releases/mozilla-1.9.3 to releases/mozilla-2.0
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Assigned: aravind)
References
Details
the branch got renamed mozilla-2.0 so the repo needs to be moved to reflect this change. if it's easier, you can delete and recreate since there's nothing unique in this repo as of yet it's just a clone of mozilla-central.
Updated•14 years ago
|
Summary: move hg.mozilla.org/releases/mozilla-1.9.3 to releases/2.0 → move hg.mozilla.org/releases/mozilla-1.9.3 to releases/mozilla-2.0
Comment 1•14 years ago
|
||
Punting to Aravind, want to be a 100% sure this is done right.
Assignee: server-ops → aravind
Assignee | ||
Comment 2•14 years ago
|
||
Done.
for the record, the command I used it "mv mozilla-1.9.3 mozilla-2.0"
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
http://hg.mozilla.org/releases/mozilla-2.0/ --> Mercurial repository not found.
Assignee | ||
Comment 4•14 years ago
|
||
(In reply to comment #3)
> http://hg.mozilla.org/releases/mozilla-2.0/ --> Mercurial repository not found.
Just fixed it.. like 10s ago.
Comment 6•14 years ago
|
||
Hey, can you add this comment "Branch development on Firefox 4.0 and Gecko 2.0."? Its what we did for mozilla191, mozilla192, so that people browsing hg.m.o can see what the repo is for.
(currently, the description for this mozilla-2.0 repo is "Unknown").
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 7•14 years ago
|
||
Done, I also added two hooks to it (treeclosure and single head)..
[hooks]
pretxnchangegroup.a_treeclosure = python:mozhghooks.treeclosure.hook
pretxnchangegroup.b_singlehead = python:mozhghooks.single_head_per_branch.hook
Let me know if you want me to remove them.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•