Lines Matching +full:google +full:- +full:java +full:- +full:format +full:- +full:diff

7 -   Read the [contributing guidelines](CONTRIBUTING.md).
8 -   Read the [Code of Conduct](CODE_OF_CONDUCT.md).
9 -   Ensure you have signed the
10     [Contributor License Agreement (CLA)](https://cla.developers.google.com/).
11 -   Check if your changes are consistent with the
12     [guidelines](#general-guidelines-and-philosophy-for-contribution).
13 -   Changes are consistent with the [Coding Style](#c-coding-style).
14 -   Run the [unit tests](#running-unit-tests).
24 …, then you'll need to sign an [individual CLA](https://code.google.com/legal/individual-cla-v1.0.h…
25 …ork, then you'll need to sign a [corporate CLA](https://code.google.com/legal/corporate-cla-v1.0.h…
35 [how to](https://help.github.com/articles/using-pull-requests/).
78     non-backward-compatible API changes without a major release. Reviewers of
80 …I review practices](https://github.com/tensorflow/community/blob/master/governance/api-reviews.md).
85 *   Full new features (e.g., a new op implementing a cutting-edge algorithm)
104 * [Java license example](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/java/src/m…
107 …github.com/tensorflow/tensorboard/blob/master/tensorboard/components/tf_backend/tf-backend.html#L2)
116 [Google C++ Style Guide](https://google.github.io/styleguide/cppguide.html).
118 Use `clang-tidy` to check your C/C++ changes. To install `clang-tidy` on ubuntu:16.04, do:
121 apt-get install -y clang-tidy
128 clang-format <my_cc_file> --style=google > /tmp/my_cc_file.cc
129 diff <my_cc_file> /tmp/my_cc_file.cc
135 [Google Python Style Guide](https://github.com/google/styleguide/blob/gh-pages/pyguide.md)
142 pylint --rcfile=tensorflow/tools/ci_build/pylintrc myfile.py
145 Note `pylint --rcfile=tensorflow/tools/ci_build/pylintrc` should run from the
150 * [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html)
151 * [Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html)
152 * [Google Shell Style Guide](https://google.github.io/styleguide/shell.xml)
153 * [Google Objective-C Style Guide](https://google.github.io/styleguide/objcguide.html)
174 …[CPU-only developer Dockerfile](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/to…
176 …om/tensorflow/tensorflow/blob/master/tensorflow/tools/dockerfiles/dockerfiles/devel-gpu.Dockerfile)
179     `tensorflow/tensorflow:devel` and `tensorflow/tensorflow:devel-gpu` for
194     export flags="--config=opt --config=cuda -k"
230     python tf_doctest.py --file=<file_path>
236     *   Use an up to date [tf-nightly](https://pypi.org/project/tf-nightly/)
237         `pip install -U tf-nightly`
253     bazel run //tensorflow/tools/docs:tf_doctest -- --module=ops.array_ops
256     The `--module` is relative to `tensorflow.python`.
261 `--config=dbg` to Bazel will build with debugging information and without
266 bazel build --config=dbg //tensorflow/tools/pip_package:build_pip_package
270 debugging information with `--config=dbg`, as issues occur on Linux if
273 you want to debug a kernel, you can compile specific files with `-g` using the
274 `--per_file_copt` bazel option. For example, if you want to debug the Identity
278 bazel build --config=dbg --per_file_copt=+tensorflow/core/kernels/identity_op.*@-g //tensorflow/too…
281 Note that the `--config=dbg` option is not officially supported.