Closed
Bug 968259
Opened 12 years ago
Closed 12 years ago
Move bzexport into version-control-tools repository
Categories
(Developer Services :: Mercurial: bzexport, defect)
Developer Services
Mercurial: bzexport
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla30
People
(Reporter: gps, Assigned: gps)
References
Details
Attachments
(3 files)
64.82 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
5.60 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
1.08 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
Bug 965330 created the hgcustom/version-control-tools repo. Let's put something in it. I say bzexport is a good first repo.
Proposal:
1) Run `hg convert` to dump the full history of https://hg.mozilla.org/users/tmielczarek_mozilla.com/bzexport into hgext/bzexport (or other bikeshedded path)
2) Update `mach mercurial-setup` to reference the new repo
3) Update the existing repo/extension to print an error message when loaded, directing them to the new location.
Does this sound reasonable?
Flags: needinfo?(ted)
Flags: needinfo?(sphink)
Comment 1•12 years ago
|
||
Fine with me. We should make this widely known so that users of bzexport can convert. Possibly even add a nag output to the existing bzexport repo for people who update from there.
Flags: needinfo?(ted)
Assignee | ||
Comment 3•12 years ago
|
||
I performed `hg convert` and moved the full history of bzexport into hgext/bzexport. Now for the non-trivial part.
Assignee | ||
Comment 4•12 years ago
|
||
The extension now aborts at load time. The error message and
documentation references the new location.
This shouldn't be pushed until mach mercurial-setup is updated to pull
the new repo.
Attachment #8371034 -
Flags: review?(ted)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → gps
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•12 years ago
|
||
Wow, Splinter really blows at formatting the patch I just uploaded.
Assignee | ||
Comment 6•12 years ago
|
||
bzexport is now pulled from its new canonical home. The old location can
be cleaned if the user agrees to it. The new location is updated in the
hgrc.
Attachment #8371041 -
Flags: review?(ted)
Comment 7•12 years ago
|
||
Comment on attachment 8371034 [details] [diff] [review]
Redirect content to new repository location
Might want to mention that you can `mach mercurial-setup` to get this installed.
Attachment #8371034 -
Flags: review?(ted) → review+
Updated•12 years ago
|
Attachment #8371041 -
Flags: review?(ted) → review+
Assignee | ||
Comment 8•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/82991c4302e0
https://hg.mozilla.org/users/tmielczarek_mozilla.com/bzexport/rev/ccdd4e552096
With mercurial-setup reference in the bzexport push.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Comment 9•12 years ago
|
||
I updated the bzexport-specific README.
http://hg.mozilla.org/hgcustom/version-control-tools/rev/781bd278967d
Updated•11 years ago
|
Assignee | ||
Comment 10•11 years ago
|
||
Trivial patch to make the dummy extension non-fatal.
Attachment #8378673 -
Flags: review?(ted)
Comment 11•11 years ago
|
||
Comment on attachment 8378673 [details] [diff] [review]
Make redirect non-fatal;
Review of attachment 8378673 [details] [diff] [review]:
-----------------------------------------------------------------
You could have just pushed this without review. :-P
Attachment #8378673 -
Flags: review?(ted) → review+
Updated•11 years ago
|
Product: Other Applications → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•