Closed
Bug 1154972
Opened 9 years ago
Closed 9 years ago
reuse upstream libvpx repository
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
FIXED
mozilla40
Tracking | Status | |
---|---|---|
firefox40 | --- | fixed |
People
(Reporter: rillian, Assigned: rillian)
Details
Attachments
(1 file)
1.64 KB,
patch
|
kinetik
:
review+
|
Details | Diff | Splinter Review |
media/libvpx/update.py does a fresh checkout of upstream libvpx every time it's run, which wastes a lot of time when testing incremental changes. Would be better to reuse a repository if there's one already there.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8593097 -
Flags: review?(kinetik)
Comment 2•9 years ago
|
||
Comment on attachment 8593097 [details] [diff] [review] Don't remove upstream repo Review of attachment 8593097 [details] [diff] [review]: ----------------------------------------------------------------- Makes sense. The fetch won't update the HEAD pointer in the current branch though, since it's only updating the remote, so I think you need an extra step to update the local branch.
Attachment #8593097 -
Flags: review?(kinetik) → review+
Comment 3•9 years ago
|
||
(In reply to Matthew Gregan [:kinetik] from comment #2) > The fetch won't update the HEAD pointer in the current branch though, since > it's only updating the remote, so I think you need an extra step to update > the local branch. e.g. with a different repo: % git rev-parse HEAD cacaae7 % git fetch cacaae7..75a0efb master -> origin/master % git rev-parse HEAD cacaae7 But you probably want to checkout 75a0efb now.
Assignee | ||
Comment 4•9 years ago
|
||
Ah, you're correct that's a change in behaviour. Previously it would do a fresh clone every time so you'd get latest master if you didn't pass --commit. In practice I always use --commit, and if not I prefer taking the current state of the repo since I can mess with it manually. This also matches how the other media update scripts work, so I think it's a reasonable change. I'll update the commit message to document the behaviour change.
Assignee | ||
Comment 5•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/9a60bf065716
Comment 6•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/9a60bf065716
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•