Closed
Bug 1042740
Opened 10 years ago
Closed 10 years ago
Add b2g32 to the push_printurls hook
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: RyanVM)
References
Details
Attachments
(1 file)
1.51 KB,
patch
|
hwine
:
review+
RyanVM
:
checked-in+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #1002640 +++
Assignee | ||
Comment 1•10 years ago
|
||
We should maybe add this to the documentation for future B2G branches as well.
Assignee | ||
Comment 2•10 years ago
|
||
Also removes the now-obsolete b2g18 and b2g26 branches.
Attachment #8460938 -
Flags: review?(hwine)
Comment 3•10 years ago
|
||
Comment on attachment 8460938 [details] [diff] [review] patch Review of attachment 8460938 [details] [diff] [review]: ----------------------------------------------------------------- lgtm
Attachment #8460938 -
Flags: review?(hwine) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Comment on attachment 8460938 [details] [diff] [review] patch http://hg.mozilla.org/hgcustom/hghooks/rev/aac2f70d8ea7
Attachment #8460938 -
Flags: checked-in+
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 5•10 years ago
|
||
https://wiki.mozilla.org/index.php?title=ReleaseEngineering%2FMerge_Duty%2FSteps&diff=999840&oldid=999522, but couldn't the hook just be taught to just work for mozilla-* so we get new b2g and esr branches without any work at all ?
Comment 6•10 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #5) > https://wiki.mozilla.org/index. > php?title=ReleaseEngineering%2FMerge_Duty%2FSteps&diff=999840&oldid=999522, > but couldn't the hook just be taught to just work for mozilla-* so we get > new b2g and esr branches without any work at all ? see bug 1011763 for the issues, and the work :)
Updated•10 years ago
|
Product: Release Engineering → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•