Closed
Bug 871739
Opened 11 years ago
Closed 11 years ago
Add valgrind and vex repositories to g.m.o
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: qdot, Unassigned)
References
Details
I need to maintain repos for valgrind and vex for b2g on gmo. Can I get these repos (b2g/valgrind and b2g/vex preferably, since they'll contain fxos specific patches for a while) made, then I'll deal with getting the svn clones going and manifest updates happening?
Comment 1•11 years ago
|
||
Follow up questions - I think I misunderstood the request in IRC: - is there an upstream repository you want to mirror (hg or git)? - where will you be committing the b2g specific changes? While we can set these up for commits on gmo, all of the current b2g/ repos live on github:mozilla-b2g/ and we mirror from there to gmo for building. Not using github is fine - just want to make sure that is your plan. :)
Flags: needinfo?(kyle)
Reporter | ||
Comment 2•11 years ago
|
||
Oh! Yeah, they're already on github. I didn't realize they got mirrored. github:mozilla-b2g/valgrind github:mozilla-b2g/vex I'm trying to keep the master branch synced to valgrind's master, and b2g specific changes live on the fxos branch while we wait to figure out whether patches on it will go to mainline valgrind. So having both of those branches replicated would be great (though fxos branch will be getting rebased on master).
Flags: needinfo?(kyle)
Comment 3•11 years ago
|
||
These are now available on http://git.mozilla.org as: b2g/valgrind.git b2g/vex.git
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•