On 2016/10/01 4:23, Ralph Giles wrote:
The change was announced here and on firefox-dev a few weeks ago. See
for example
https://groups.google.com/d/msg/mozilla.dev.platform/LOC83qKUPfk/cZtmaEbOAwAJ
Obviously I missed it during a busy trip. Thank you.
(It would be nice to have the announcement
On Fri, Sep 30, 2016 at 12:33 PM, Gregory Szorc wrote:
> `mach mercurial-setup` does an `hg pull` from hg.mozilla.org to obtain the
> version-control-tools repository, which is where most of the logic for `mach
> mercurial-setup` lives (because we have a nice testing harness in
> version-control-t
`mach mercurial-setup` does an `hg pull` from hg.mozilla.org to obtain the
version-control-tools repository, which is where most of the logic for
`mach mercurial-setup` lives (because we have a nice testing harness in
version-control-tools). `mach mercurial-setup` doesn't pin the hash when
invoking
The change was announced here and on firefox-dev a few weeks ago. See
for example
https://groups.google.com/d/msg/mozilla.dev.platform/LOC83qKUPfk/cZtmaEbOAwAJ
It might be nice if `mach mercurial-setup` did this kind of update?
-r
On Fri, Sep 30, 2016 at 12:18 PM, ISHIKAWA,chiaki wrote:
> In
In the last few days, hg.mozilla.org certificate fingerprint seems to
have changed.
I noticed this because the trial to update local copy of mozilla-central
repository within C-C repository failed due to
m-central/mozilla', 'https://hg.mozilla.org/mozilla-central/']
pulling from https://hg.mo
5 matches
Mail list logo
