Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AMO validation] # is not a valid JS comment character (Issue #133) #134

Closed
wants to merge 2 commits into from
Closed

Conversation

tonymec
Copy link
Contributor

@tonymec tonymec commented Apr 26, 2013

No description provided.

tonymec added 2 commits April 26, 2013 11:07
issue #133: # is not a valid Javascript comment character
Issue #133: # is not a valid Javascript comment character
@ghost ghost assigned tonymec Apr 26, 2013
@tonymec
Copy link
Contributor Author

tonymec commented Apr 26, 2013

@whimboo : r?

@xabolcs
Copy link
Collaborator

xabolcs commented Apr 26, 2013

Hmm, tonymec:master seems to be outdated. :-/
You based the patch on commit 1dfa467 which is very outdated - it's MPL1.1.

If you would keep this pull, then you should merge in mozilla/master, or simply close this request and rebase this two changeset.

@tonymec
Copy link
Contributor Author

tonymec commented Apr 26, 2013

Ah, sorry, it told me it was up-to-date. About MPL 1.1: that's the license AMO says we're using.

@tonymec tonymec closed this Apr 26, 2013
@xabolcs
Copy link
Collaborator

xabolcs commented Apr 26, 2013

And please use * like in the other js files:

/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */

@whimboo
Copy link
Contributor

whimboo commented Apr 26, 2013

Ah, sorry, it told me it was up-to-date. About MPL 1.1: that's the license AMO says we're using.

Really? I have updated the AMO entry yesterday to MPL 2. Might be it will update it with the not yet reviewed 3.5 release.

@xabolcs
Copy link
Collaborator

xabolcs commented Apr 26, 2013

Really? I have updated the AMO entry yesterday to MPL 2. Might be it will update it with the not yet reviewed 3.5 release.

For the currently displayed 3.4 AMO says:

Source code released under Custom License

For the currently queued 3.5 AMO says:

Source code released under Mozilla Public License, version 2.0

And the relicense was done by #39 and #98 (landed in v3.4).

@whimboo
Copy link
Contributor

whimboo commented Apr 26, 2013

Looks like you cannot change the license for older entries but it only applies to the current one. So we cannot change this anymore. I wouldn't worry that much about it.

@tonymec
Copy link
Contributor Author

tonymec commented Apr 26, 2013

Yeah, apparently I wasn't up-to-date on that either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants