Migrate pushlog into version-control-tools repo

RESOLVED FIXED

Status

Developer Services
Mercurial: hg.mozilla.org
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: gps, Assigned: gps)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
I plan to migrate https://hg.mozilla.org/hgcustom/pushlog into version-control-tools. One more step towards bringing all the version-control-tools code under one roof.

Once this migration is in place, I'd like to unify the pushlog code as an extension (rather than hook + web code). That will make it easier to add pushlog data to |hg pull| and to make our repository syncing solution simpler and less error prone.
(Assignee)

Comment 1

3 years ago
Created attachment 8486599 [details] [diff] [review]
Move pushlog into version-control-tools

Looking for a rubber stamp approval for this conversion.
Attachment #8486599 - Flags: review?(laura)
(Assignee)

Updated

3 years ago
Assignee: nobody → gps
Status: NEW → ASSIGNED
(Assignee)

Updated

3 years ago
Blocks: 1065050

Updated

3 years ago
Attachment #8486599 - Flags: review?(laura) → review+
(Assignee)

Comment 2

3 years ago
https://hg.mozilla.org/hgcustom/pushlog/rev/add5588ce789
(Assignee)

Updated

3 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Assignee)

Updated

3 years ago
Blocks: 1074491
Product: Release Engineering → Developer Services
For the record, https://hg.mozilla.org/hgcustom/version-control-tools/rev/e3d700020d5c is the last tip of https://hg.mozilla.org/hgcustom/pushlog as landed on version-control-tools.
You need to log in before you can comment on or make changes to this bug.