On Dec 26, 2012, at 12:56 PM, Dave Hylands wrote:
> Hi Lucas,
>
> Hmm. That works for me.
>
> Did you grab the latest of the B2G repository?
>
> You need to figure out the repository name (it will be called origin or b2g).
>
> git remote -v
>
> will show the names of the remotes. For me, I
Hi Lucas,
- Original Message -
> From: "Lucas Adamski"
> To: "Dave Hylands"
> Cc: "dev-b2g"
> Sent: Wednesday, December 26, 2012 11:38:25 AM
> Subject: Re: [b2g] ./config.sh now defaults to nightly branch
>
> Hi Dave,
>
> I tri
Hi Dave,
I tried running this but "./config.sh otoro" results in "error: revision otoro
in manifests not found". Any ideas? :)
Lucas.
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Hi Eric,
- Original Message -
> From: "Eric Shepherd"
> To: "mozilla dev b2g"
> Cc: "dev-b2g"
> Sent: Wednesday, December 26, 2012 8:02:16 AM
> Subject: Re: [b2g] ./config.sh now defaults to nightly branch
>
> > You can update your
> You can update your repositories by reruning "./config.sh PHONE"
> This does a repo sync so take the normal precautions of committing
> your changes.
Dave, is this something that's still relevant? That is, if we build our own
B2G, do we need to do this before we do our next build if we haven't
Hi everyone,
The b2g manifests have been changed to point to
http://git.mozilla.org/releases/gecko.git and that repository contains a master
branch which hasn't been updated in over a week, making the only usable branch
be the gecko-18 branch (aka nighty).
Since our build instructions are to j
