diff options
| author | Eric Erfanian <erfanian@google.com> | 2017-06-22 09:39:08 -0700 |
|---|---|---|
| committer | Eric Erfanian <erfanian@google.com> | 2017-06-22 17:23:58 +0000 |
| commit | 842a9777de13bebb1c82f9d57222c52f9ddec558 (patch) | |
| tree | 742285fa641f62ba0b358a65a452f4f65db04ce2 /CONTRIBUTING | |
| parent | a8a71b12c67ca852382e94d5e6d5d04430529902 (diff) | |
Update AOSP Dialer source from internal google3 repository at
cl/159771812.
Test: make, treehugger
This CL updates the AOSP Dialer source with all the changes that have
gone into the private google3 repository. This includes all the
changes from cl/159428781 (6/19/2017) to cl/159771812 (6/22/2017).
These changes track the dialer V11 release.
This goal of these drops is to keep the AOSP source in sync with the
internal google3 repository. Currently these sync are done by hand
with very minor modifications to the internal source code.
See the Android.mk file for list of modifications.
Merged-In: I39aba7e972bac6e5864e70ed693849d90ecd7e08
Change-Id: Ia87877f7ae67c5b56078477b8b08082de1355315
Diffstat (limited to 'CONTRIBUTING')
| -rw-r--r-- | CONTRIBUTING | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING deleted file mode 100644 index 2827b7d3f..000000000 --- a/CONTRIBUTING +++ /dev/null @@ -1,27 +0,0 @@ -Want to contribute? Great! First, read this page (including the small print at the end). - -### Before you contribute -Before we can use your code, you must sign the -[Google Individual Contributor License Agreement] -(https://cla.developers.google.com/about/google-individual) -(CLA), which you can do online. The CLA is necessary mainly because you own the -copyright to your changes, even after your contribution becomes part of our -codebase, so we need your permission to use and distribute your code. We also -need to be sure of various other things—for instance that you'll tell us if you -know that your code infringes on other people's patents. You don't have to sign -the CLA until after you've submitted your code for review and a member has -approved it, but you must do it before we can put your code into our codebase. -Before you start working on a larger contribution, you should get in touch with -us first through the issue tracker with your idea so that we can help out and -possibly guide you. Coordinating up front makes it much easier to avoid -frustration later on. - -### Code reviews -All submissions, including submissions by project members, require review. We -use Github pull requests for this purpose. - -### The small print -Contributions made by corporations are covered by a different agreement than -the one above, the -[Software Grant and Corporate Contributor License Agreement] -(https://cla.developers.google.com/about/google-corporate). |