Closed Bug 1120196 Opened 10 years ago Closed 10 years ago

Update mercurial requirement to 3.2.x

Categories

(Webtools Graveyard :: Elmo, defect)

Product:
Webtools Graveyard
Component:
Elmo
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Pike, Assigned: Pike)

References

Details

For being able to update mercurial in a10n, we need to update it in elmo. We're currently on 2.8, we should go for 3.2.x. Entry points to check are mercurial.commands.add mercurial.commands.addremove mercurial.commands.clone mercurial.commands.commit mercurial.commands.copy mercurial.commands.init mercurial.commands.merge mercurial.commands.pull mercurial.commands.remove mercurial.commands.rename mercurial.commands.update mercurial.copies._chain mercurial.copies.pathcopies mercurial.dispatch.dispatch mercurial.dispatch.request mercurial.error.RepoError mercurial.error.RepoLookupError mercurial.hg.repository mercurial.ui.ui mercurial.worker mercurial.worker._startupcost in shipping and pushes.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee: nobody → l10n
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.