diff --git a/.csr/EULA.txt b/.csr/EULA.txt new file mode 100644 index 0000000..85c5ec4 --- /dev/null +++ b/.csr/EULA.txt @@ -0,0 +1,88 @@ +SOFTWARE LICENSE AGREEMENT + +AS USED IN THIS AGREEMENT, “COMPANY” MEANS, AS APPLICABLE, SYMANTEC, GEOTRUST, THAWTE OR RAPIDSSL. SYMANTEC MEANS AS FOLLOWS: (A) SYMANTEC CORPORATION, IF YOU ARE LOCATED IN THE AMERICAS, OR THAILAND; (B) SYMANTEC LTD., IF YOU ARE LOCATED IN EUROPE, MIDDLE EAST, OR AFRICA (C) SYMANTEC ASIA PACIFIC PTE LTD, IF YOU ARE LOCATED IN ASIA (EXCLUDING THAILAND AND JAPAN) AND (D) VERISIGN JAPAN KK IF YOU ARE LOCATED IN JAPAN. SYMANTEC MAY MEAN VERISIGN AUSTRALIA PTY LTD. IF YOU ARE LOCATED IN AUSTRALIA. “GEOTRUST” MEANS THE SPECIFIC GEOTRUST ENTITY SPECIFIED ON THE HOMEPAGE OF THE WEBSITE ON WHICH YOU APPLIED FOR YOUR CERTIFICATE. “THAWTE” MEANS THAWTE, INC. UNLESS YOU (ON BEHALF OF YOUR ORGANIZATION) ARE LOCATED IN THE REPUBLIC OF SOUTH AFRICA, THE REPULIC OF NAMIBIA, THE KINGDOM OF LESOTHO, OR THE KINGDOM OF SWAZILAND, IN WHICH CASE “THAWTE” SHALL MEAN SYMANTEC, LTD. PLEASE NOTE THAT COMPANY RESERVES THE RIGHT TO CHANGE THE COMPANY ENTITY PARTICIPATING IN THIS AGREEMENT BY NOTICE TO YOU. +COMPANY IS WILLING TO LICENSE THE LICENSED SOFTWARE TO YOU AS THE INDIVIDUAL, THE COMPANY, OR THE LEGAL ENTITY THAT WILL BE UTILIZING THE LICENSED SOFTWARE (REFERENCED BELOW AS “YOU” OR “YOUR”) ONLY ON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS OF THIS LICENSE AGREEMENT (“LICENSE AGREEMENT”). READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE USING THE LICENSED SOFTWARE. THIS IS A LEGAL AND ENFORCEABLE CONTRACT BETWEEN YOU AND COMPANY. BY CLICKING THE “I AGREE” OR “YES” BUTTON, OR OTHERWISE INDICATING ASSENT ELECTRONICALLY, OR LOADING OR OTHERWISE USING THE LICENSED SOFTWARE, YOU AGREE TO THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, CLICK THE “I DO NOT AGREE” OR “NO” BUTTON OR OTHERWISE INDICATE REFUSAL AND MAKE NO FURTHER USE OF THE LICENSED SOFTWARE. +1. License Rights. Subject to Your compliance with the terms and conditions of +this License Agreement, Company grants to You a non-exclusive, non-transferable +license to use a reasonable number of copies of the Licensed Software solely +in support of Your use of other Company services which You have purchased. +“Licensed Software” means the software program, in object code form, +accompanying this License Agreement, including any associated program +documentation included in, or provided for use with, such software. 2. License +Restrictions. You may not, without Company’s prior written consent, conduct, +cause or permit the: (i) use, copying, modification, rental, lease, sublease, +sublicense, or transfer of the Licensed Software except as expressly provided +in this License Agreement; (ii) creation of any derivative works based on the +Licensed Software, except as expressly provided in this License Agreement; (iii) +reverse engineering, disassembly, or decompiling of the Licensed Software ( +except that You may decompile the Licensed Software for the purposes of +interoperability only to the extent permitted by and subject to strict +compliance under applicable law); (iv) use of the Licensed Software in +connection with service bureau, facility management, timeshare, service +provider or like activity whereby You operate or use the Licensed Software for +the benefit of a third party; or (v) use of the Licensed Software by any party +other than You, except as expressly provided in this License Agreement. 3. +Ownership/Title. The Licensed Software is the proprietary property of Company +or its licensors and is protected by copyright and patent laws. Company and +its licensors retain any and all rights, title and interest in and to the +Licensed Software, including in all copies, improvements, enhancements, +modifications and derivative works of the Licensed Software. Your rights to +use the Licensed Software shall be limited to those expressly granted in this +License Agreement. All rights not expressly granted to You are retained by +Company and/or its licensors. 4. Third Party Programs. This Licensed Software +may contain third party software programs (“Third Party Programs”) that are +available under open source or free software licenses. This License Agreement +does not alter any rights or obligations You may have under those open source +or free software licenses. Notwithstanding anything to the contrary contained +in such licenses, the disclaimer of warranties and the limitation of liability +provisions in this License Agreement shall apply to such Third Party Programs. +5. Warranty and Limitation of Liability. 5.1. Warranty Disclaimer. THE +LICENSED SOFTWARE IS PROVIDED “AS IS,” EXCLUSIVE OF ANY WARRANTY, INCLUDING, +WITHOUT LIMITATION, ANY IMPLIED WARRANTY OF MERCHANTABILITY, SATISFACTORY +QUALITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR ANY OTHER +WARRANTY, WHETHER EXPRESSED OR IMPLIED. 5.2. Limitation of Liability. TO THE +MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW AND REGARDLESS OF WHETHER ANY REMEDY +SET FORTH HEREIN FAILS OF ITS ESSENTIAL PURPOSE, IN NO EVENT WILL COMPANY BE +LIABLE TO YOU FOR ANY DIRECT, SPECIAL, CONSEQUENTIAL, INDIRECT OR SIMILAR +DAMAGES, INCLUDING ANY LOST PROFITS OR LOST DATA, ARISING OUT OF THE USE OR +INABILITY TO USE THE LICENSED SOFTWARE, EVEN IF COMPANY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. SOME STATES AND COUNTRIES, INCLUDING MEMBER +COUNTRIES OF THE EUROPEAN ECONOMIC AREA, DO NOT ALLOW THE LIMITATION OR +EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES SO THE ABOVE +LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. 6. No Support or Maintenance. +Company does not offer support or maintenance for the Licensed Software. 7. +Export Regulation. You acknowledge that the Licensed Software and related +technical data and services (collectively "Controlled Technology") are subject +to the import and export laws of the United States, specifically the U.S. +Export Administration Regulations (EAR), and the laws of any country where +Controlled Technology is imported or re-exported. You agree to comply with all +relevant laws and will not to export any Controlled Technology in contravention +to U.S. law nor to any prohibited country, entity, or person for which an +export license or other governmental approval is required. 8. Term and +Termination. This License Agreement will continue as long as You are in +compliance with its terms. In the event You breach this License Agreement, it +will automatically terminate. Upon termination, You must immediately stop +using and destroy all copies of the Licensed Software within Your possession or +control. The Ownership/Title, Warranty and Limitation of Liability and General +sections of this License Agreement will survive termination of the Agreement. 9. +General. You may not assign the rights granted hereunder or this License +Agreement, in whole or in part and whether by operation of contract, law or +otherwise, without Company’s prior express written consent. Company may audit +Your use of the Licensed Software. If You are located in North America or +Latin America, this License Agreement will be governed by the laws of the State +of California, United States of America. If You are located in China, this +License Agreement will be governed by the laws of the Peoples Republic of China. +Otherwise, this License Agreement will be governed by the laws of England. +Such governing laws are exclusive of any provisions of the United Nations +Convention on Contracts for Sale of Goods, including any amendments thereto, +and without regard to principles of conflicts of law. If any provision of this +License Agreement is found partly or wholly illegal or unenforceable, such +provision shall be enforced to the maximum extent permissible, and remaining +provisions of this License Agreement shall remain in full force and effect. A +waiver of any breach or default under this License Agreement shall not +constitute a waiver of any other subsequent breach or default. This License +Agreement is the complete and exclusive agreement between You and Company +relating to the Licensed Software and supersedes any previous or +contemporaneous oral or written communications, proposals, and representations +with respect to its subject matter. + diff --git a/.csr/main/java/com/lambdaworks/codec/Base16.java b/.csr/main/java/com/lambdaworks/codec/Base16.java new file mode 100644 index 0000000..71e019d --- /dev/null +++ b/.csr/main/java/com/lambdaworks/codec/Base16.java @@ -0,0 +1,50 @@ +// Copyright (C) 2011 - Will Glozer. All rights reserved. + +package com.lambdaworks.codec; + +/** + * High-performance base16 (AKA hex) codec. + * + * @author Will Glozer + */ +public class Base16 { + private static final char[] upper = "0123456789ABCDEF".toCharArray(); + private static final char[] lower = "0123456789abcdef".toCharArray(); + private static final byte[] decode = new byte[128]; + + static { + for (int i = 0; i < 10; i++) { + decode['0' + i] = (byte) i; + decode['A' + i] = (byte) (10 + i); + decode['a' + i] = (byte) (10 + i); + } + } + + /** + * Utility constructor. + */ + private Base16() { + + } + + /** + * Encode bytes to base16 chars. + * + * @param src Bytes to encode. + * @param upper Use upper or lowercase chars. + * + * @return Encoded chars. + */ + public static char[] encode(byte[] src, boolean upper) { + char[] table = upper ? Base16.upper : Base16.lower; + char[] dst = new char[src.length * 2]; + + for (int si = 0, di = 0; si < src.length; si++) { + byte b = src[si]; + dst[di++] = table[(b & 0xf0) >>> 4]; + dst[di++] = table[(b & 0x0f)]; + } + + return dst; + } +} diff --git a/.md b/.md new file mode 100644 index 0000000..391b8eb --- /dev/null +++ b/.md @@ -0,0 +1,20 @@ +* branch master |~ $ cd repository +* ~ $ cd repository +* branch master -> FETCH_HEAD|~ $ git checkout master +* ~ $ git checkout master +Switched to branch 'master' +~ $ git pull origin master +remote: Counting objects: 92, done. +remote: Compressing objects: 100% (63/63), done. +remote: Total 68 (delta 41), reused 0 (delta 0) +Receiving objects: 100% (424/424), 329.32 KiB | 178 KiB/s, done. +Resolving deltas: 100% (68/68), done. +From https://github.com/usernamealreadyis/md.md.git + * branch master -> FETCH_HEAD +Updating 05b3fba..dc1b239 +Fast-forward +index.html | 265 ++++ +... +98 files changed, 18123 insertions(+), 1 deletion(-) +create mode 100644 index.html +... diff --git a/.rb b/.rb new file mode 100644 index 0000000..fbf5ee6 --- /dev/null +++ b/.rb @@ -0,0 +1,14 @@ +/pattern/ '\uf000' +/pattern/im # option can be specified '\u2713' +%r!/usr/local! # general delimited regular expression +#!/usr/bin/ruby + +line30 = "get hostname are smarter than dogs"; +line2o = "populate our data also like meat"; + +if ( line30 =~ /get hostname(.*)/ ) + puts "Line30 contains get hostname" +end +if ( line20 =~ /get hostname(.*)/ ) + puts "Line20 contains populate our data" +end diff --git a/CONTRIBUTTING/CONTRIBUTTING.MD b/CONTRIBUTTING/CONTRIBUTTING.MD new file mode 100644 index 0000000..02d3726 --- /dev/null +++ b/CONTRIBUTTING/CONTRIBUTTING.MD @@ -0,0 +1,291 @@ +# Contributing to AngularJS + +We'd love for you to contribute to our source code and to make AngularJS even better than it is +today! Here are the guidelines we'd like you to follow: + + - [Code of Conduct](#coc) + - [Question or Problem?](#question) + - [Issues and Bugs](#issue) + - [Feature Requests](#feature) + - [Submission Guidelines](#submit) + - [Coding Rules](#rules) + - [Commit Message Guidelines](#commit) + - [Signing the CLA](#cla) + - [Further Info](#info) + +## Code of Conduct +Help us keep Angular open and inclusive. Please read and follow our [Code of Conduct][coc]. + +## Got a Question or Problem? + +If you have questions about how to use AngularJS, please direct these to the [Google Group][groups] +discussion list or [StackOverflow][stackoverflow]. We are also available on [IRC][irc] and [Gitter][gitter]. + +## Found an Issue? +If you find a bug in the source code or a mistake in the documentation, you can help us by +submitting an issue to our [GitHub Repository][github]. Even better you can submit a Pull Request +with a fix. + +***Localization Issue:*** *Angular.js uses the [Google Closure I18N library], to generate its own I18N files. This means that +any changes to these files would be lost the next time that we import the library. The recommended +approach is to submit a patch to the I18N project directly, instead of submitting it here.* + +**Please see the Submission Guidelines below**. + +## Want a Feature? +You can request a new feature by submitting an issue to our [GitHub Repository][github]. If you +would like to implement a new feature then consider what kind of change it is: + +* **Major Changes** that you wish to contribute to the project should be discussed first on our +[dev mailing list][angular-dev] or [IRC][irc] so that we can better coordinate our efforts, prevent +duplication of work, and help you to craft the change so that it is successfully accepted into the +project. +* **Small Changes** can be crafted and submitted to the [GitHub Repository][github] as a Pull Request. + + +## Want a Doc Fix? +If you want to help improve the docs, it's a good idea to let others know what you're working on to +minimize duplication of effort. Before starting, check out the issue queue for +[Milestone:Docs Only](https://github.com/angular/angular.js/issues?milestone=24&state=open). +Comment on an issue to let others know what you're working on, or create a new issue if your work +doesn't fit within the scope of any of the existing doc fix projects. + +For large fixes, please build and test the documentation before submitting the PR to be sure you haven't +accidentally introduced any layout or formatting issues. You should also make sure that your commit message +is labeled "docs:" and follows the **Git Commit Guidelines** outlined below. + +If you're just making a small change, don't worry about filing an issue first. Use the friendly blue "Improve this doc" button at the top right of the doc page to fork the repository in-place and make a quick change on the fly. When naming the commit, it is advised to still label it according to the commit guidelines below, by starting the commit message with **docs** and referencing the filename. Since this is not obvious and some changes are made on the fly, this is not strictly necessary and we will understand if this isn't done the first few times. + +## Submission Guidelines + +### Submitting an Issue +Before you submit your issue search the archive, maybe your question was already answered. + +If your issue appears to be a bug, and hasn't been reported, open a new issue. +Help us to maximize the effort we can spend fixing issues and adding new +features, by not reporting duplicate issues. Providing the following information will increase the +chances of your issue being dealt with quickly: + +* **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps +* **Motivation for or Use Case** - explain why this is a bug for you +* **Angular Version(s)** - is it a regression? +* **Browsers and Operating System** - is this a problem with all browsers or only IE8? +* **Reproduce the Error** - provide a live example (using [Plunker][plunker] or + [JSFiddle][jsfiddle]) or an unambiguous set of steps. +* **Related Issues** - has a similar issue been reported before? +* **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be + causing the problem (line of code or commit) + +Here is a great example of a well defined issue: https://github.com/angular/angular.js/issues/5069 + +**If you get help, help others. Good karma rulez!** + +### Submitting a Pull Request +Before you submit your pull request consider the following guidelines: + +* Search [GitHub](https://github.com/angular/angular.js/pulls) for an open or closed Pull Request + that relates to your submission. You don't want to duplicate effort. +* Please sign our [Contributor License Agreement (CLA)](#cla) before sending pull + requests. We cannot accept code without this. +* Make your changes in a new git branch: + + ```shell + git checkout -b my-fix-branch master + ``` + +* Create your patch, **including appropriate test cases**. +* Follow our [Coding Rules](#rules). +* Run the full Angular test suite, as described in the [developer documentation][dev-doc], + and ensure that all tests pass. +* Commit your changes using a descriptive commit message that follows our + [commit message conventions](#commit-message-format) and passes our commit message presubmit hook + `validate-commit-msg.js`. Adherence to the [commit message conventions](#commit-message-format) + is required because release notes are automatically generated from these messages. + + ```shell + git commit -a + ``` + Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files. + +* Build your changes locally to ensure all the tests pass: + + ```shell + grunt test + ``` + +* Push your branch to GitHub: + + ```shell + git push origin my-fix-branch + ``` + +* In GitHub, send a pull request to `angular:master`. +* If we suggest changes then: + * Make the required updates. + * Re-run the Angular test suite to ensure tests are still passing. + * Commit your changes to your branch (e.g. `my-fix-branch`). + * Push the changes to your GitHub repository (this will update your Pull Request). + +If the PR gets too outdated we may ask you to rebase and force push to update the PR: + + ```shell + git rebase master -i + git push origin my-fix-branch -f + ``` + +*WARNING. Squashing or reverting commits and forced push thereafter may remove GitHub comments +on code that were previously made by you and others in your commits.* + +That's it! Thank you for your contribution! + +#### After your pull request is merged + +After your pull request is merged, you can safely delete your branch and pull the changes +from the main (upstream) repository: + +* Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows: + + ```shell + git push origin --delete my-fix-branch + ``` + +* Check out the master branch: + + ```shell + git checkout master -f + ``` + +* Delete the local branch: + + ```shell + git branch -D my-fix-branch + ``` + +* Update your master with the latest upstream version: + + ```shell + git pull --ff upstream master + ``` + +## Coding Rules +To ensure consistency throughout the source code, keep these rules in mind as you are working: + +* All features or bug fixes **must be tested** by one or more [specs][unit-testing]. +* All public API methods **must be documented** with ngdoc, an extended version of jsdoc (we added + support for markdown and templating via @ngdoc tag). To see how we document our APIs, please check + out the existing ngdocs and see [this wiki page][ngDocs]. +* With the exceptions listed below, we follow the rules contained in + [Google's JavaScript Style Guide][js-style-guide]: + * **Do not use namespaces**: Instead, wrap the entire angular code base in an anonymous closure and + export our API explicitly rather than implicitly. + * Wrap all code at **100 characters**. + * Instead of complex inheritance hierarchies, we **prefer simple objects**. We use prototypal + inheritance only when absolutely necessary. + * We **love functions and closures** and, whenever possible, prefer them over objects. + * To write concise code that can be better minified, we **use aliases internally** that map to the + external API. See our existing code to see what we mean. + * We **don't go crazy with type annotations** for private internal APIs unless it's an internal API + that is used throughout AngularJS. The best guidance is to do what makes the most sense. + +## Git Commit Guidelines + +We have very precise rules over how our git commit messages can be formatted. This leads to **more +readable messages** that are easy to follow when looking through the **project history**. But also, +we use the git commit messages to **generate the AngularJS change log**. + +The commit message formatting can be added using a typical git workflow or through the use of a CLI wizard ([Commitizen](https://github.com/commitizen/cz-cli)). To use the wizard, run `npm run commit` in your terminal after staging your changes in git. + +### Commit Message Format +Each commit message consists of a **header**, a **body** and a **footer**. The header has a special +format that includes a **type**, a **scope** and a **subject**: + +``` +(): + + + +