Closed
Bug 1427696
Opened 7 years ago
Closed 7 years ago
Developers who are allowed to push to inbound should be allowed to push to htmlparser
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: hsivonen, Unassigned)
References
Details
Bug 1378079 comment 55 and bug 1424548 comment 22 indicate that not everyone who can push to mozilla-inbound can push to htmlparser.
Could that be remedied, please, so that it's easier to keep the htmlparser repo in sync with Firefox code?
Comment 1•7 years ago
|
||
There are no special privileges on projects/htmlparser. The repo is owned by the scm_level_2 group, which is different from most of the Firefox repos (which are scm_level_3).
At least in bug 1424548, the issue was attempting to push to https://hg.mozilla.org/projects/htmlparser instead of ssh://hg.mozilla.org/projects/htmlparser. The error message is not very helpful. Improving that /may/ require upstream changes to Mercurial. Those would best be requested by filing a bug at https://bz.mercurial-scm.org/. Although we could potentially make some HTTP server configuration changes to achieve a similar result. Mercurial is in the better position to emit a better error message though.
Comment 2•7 years ago
|
||
(In reply to Gregory Szorc [:gps] from comment #1)
> At least in bug 1424548, the issue was attempting to push to
> https://hg.mozilla.org/projects/htmlparser instead of
> ssh://hg.mozilla.org/projects/htmlparser.
Thanks. That worked. I had the wrong push path.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•