[Bug 836105] freezing revsion attributes for the v1.0.0 branch

[jhford]

Like before, this PR sets the repositories we control to the v1.0.0 branch and the ones that we don't to the current HEAD revision of the remote.

@cgjones -- sorry for the spam, i created my remote in the repository with the wrong URL (facepalm)

[jhford]

@cgjones or @michaelwu -- what do you guys think? I don't think it's reasonable to do this without using an XML parser and serializer.

[michaelwu]

I don't mind clobbering the whitespace for branches. r=me. I'll just assume you did the right thing here since there's no reasonable way for humans to check all these hashes.

[michaelwu]

BTW, by HEAD, I hope you mean the ref that the project is using. Not all projects point to master

[jhford]

HEAD would be a symbolic reference to whatever branch that repo put the repository on.

[jhford]

I have the script that I used to generate the diffs attached to the bugzilla bug, but I'm rerunning it with a slight change to freeze in the commits from the git.mozilla.org/b2g repositories and set the upstream attribute correctly.

[jhford]

@michaelwu I've taken the comments from the email thread and recreated the changes for v1-train and v1.0.0, basically I'm doing what |repo manifest| does, and putting the commit into revision attribute and the branch for git.mozilla.org/b2g in the undocumented upstream attribute.

Does this r=mwu hold for these changes, and those on v1-train as well? (PR 50)

[michaelwu]

Looks about right to me. r=me