Closed
Bug 974219
Opened 10 years ago
Closed 10 years ago
Move qimportbz into the new https://hg.mozilla.org/hgcustom/version-control-tools repo
Categories
(Developer Services :: Mercurial: qimportbz, defect)
Developer Services
Mercurial: qimportbz
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
Attachments
(1 file)
27.01 KB,
patch
|
Details | Diff | Splinter Review |
See bug 968958 for context. Rob, are you ok with this?
Flags: needinfo?(tellrob)
Assignee | ||
Updated•10 years ago
|
Summary: More qimportbz into the new https://hg.mozilla.org/hgcustom/version-control-tools repo → Move qimportbz into the new https://hg.mozilla.org/hgcustom/version-control-tools repo
Comment 1•10 years ago
|
||
Does this mean that user clones of the qimportbz extension will have to change the URL from which they pull? Or will a redirect be set up server-side?
Flags: needinfo?(emorley)
Assignee | ||
Comment 2•10 years ago
|
||
The latter, there is no easy way to do the former. I was thinking we'd just use a similar approach to bug 968259. ie: users of mach mercurial-setup will get prompted to update, and others will see a warning when next manually pulling the qimportbz repo.
Flags: needinfo?(emorley)
Comment 3•10 years ago
|
||
I think this is fine. Updating the extension in the old location to warn users is a good idea. I'm not sure if it would be a good idea to introduce a harder nag later (say, 6 months) to get any stragglers.
Flags: needinfo?(tellrob)
Assignee | ||
Comment 4•10 years ago
|
||
Using the script I attached in bug 976514: [/c/src/vctools]$ ~/Desktop/repo-import.sh ../qimportbz/ hgext/qimportbz Import ../qimportbz/ into the subdirectory hgext/qimportbz? (y/n)?y pulling from https://hg.mozilla.org/hgcustom/version-control-tools/ searching for changes no changes found pulling from https://hg.mozilla.org/users/robarnold_cmu.edu/qimportbz/ searching for changes no changes found scanning source... sorting... converting... 80 Initial commit spliced in ['63384b427fbe20e1f9d2e24a3501ddf14654a439'] as parents of ea716d926c130c965d938c31bfc8af622e874b8f 79 Removed get_input 78 Added .hgignore 77 Use description instead of attachid for patch names 76 Started using optparse, added verbose, quiet and dry-run options 75 Sanitize patch names ... <snip> Pushed as: https://hg.mozilla.org/hgcustom/version-control-tools/pushloghtml?changeset=d67373dd5bb4
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•10 years ago
|
||
Create README & remove redundant hgignore, post import: https://hg.mozilla.org/hgcustom/version-control-tools/rev/b5debc0f283d
Assignee | ||
Comment 6•10 years ago
|
||
With qimportbz imported into the vcstools repo & bug 976892 propagated around the tree, it's time to land the qimportbz equivalent of bug 968259.
Assignee | ||
Comment 7•10 years ago
|
||
Redirect landed on: https://hg.mozilla.org/users/robarnold_cmu.edu/qimportbz/rev/532a85be8b49
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Other Applications → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•