Closed Bug 545877 Opened 15 years ago Closed 15 years ago

amo-js and SVN are out of sync

Categories

(addons.mozilla.org Graveyard :: Code Quality, defect)

Product:
addons.mozilla.org Graveyard
Component:
Code Quality
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: wenzel, Assigned: davedash)

Details

A fresh git-svn checkout does not match the commit IDs on http://github.com/davedash/amo-js . STR: - git svn clone https://svn.mozilla.org/addons/trunk/site/app/webroot/js amo-js - cd amo-js; git log compare any of the commit IDs to the ones on http://github.com/davedash/amo-js/commits/master , they don't match. This can probably be fixed by checking out a pristine copy off SVN as shown above and force-pushing it over amo-js on github, but I didn't want to mess with other people's repos, so I am filing this bug.
apparently, git on khan is playing a prank on us here, by being incompatible with newer versions of git-svn (wtf?). WONTFIX.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.