Hi. This is awesome, upgrading and configuring cinnabar had always been a sore point
But I just noticed that it appears to pull from git-cinnabar master branch… I had to run bootstrap on android yesterday, which upgraded git-cinnabar (requiring a git upgrade) and had to run it again today. which too requires a git upgrade git upgrade takes a significant time. Wouldn’t it be better to follow the release branch instead of master? JY > On 17 Aug 2018, at 9:50 am, Panos Astithas <p...@mozilla.com> wrote: > > Hi all, > > since bug 1257478 landed in m-c earlier today, you should now be using 'mach > vcs-setup' instead of 'mach mercurial-setup'. Nothing else changes in your > workflow (e.g. 'mach mercurial-setup -u' becomes 'mach vcs-setup -u') and the > spell checker will suggest vcs-setup if you try to use mercurial-setup. > > If you are a git-cinnabar user, your workflow is now supported. 'mach > vcs-setup --git' will fetch the latest recommended version of git-cinnabar > and configure it for you. The --update-only flag is also available for git, > so it would be a good idea to run 'mach vcs-setup --git --update-only' (or > 'mach vcs-setup -gu') every now and then to make sure everything is up to > date. > > 'mach bootstrap' will also offer to update and configure your git-cinnabar > environment if a git checkout is detected. > > Cheers, > Panos > > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
