Home
last modified time | relevance | path

Searched full:release_notes (Results 1 – 25 of 34) sorted by relevance

12

/external/skia/
DPRESUBMIT_test.py34 MockFile('RELEASE_NOTES.md', ''),
45 'Do not edit RELEASE_NOTES.md'))
50 MockFile('RELEASE_NOTES.md', ''),
/external/curl/packages/vms/
Dbuild_gnv_curl_release_notes.com94 /out='base_file'.release_notes
96 $ purge 'base_file'.release_notes
97 $ rename 'base_file.release_notes ;1
Dclean_gnv_curl.com118 $ file = "lcl_root:[.packages.vms]curl-*.release_notes"
121 $ file = "lcl_root:[.packages.vms]curl_d-*.release_notes"
Dbuild_gnv_curl_pcsi_desc.com378 $write pdsc " information RELEASE_NOTES phase after ;"
480 " file ""[SYSHLP]''filename_base'.release_notes"" release notes ;"
Dbuild_gnv_curl_pcsi_text.com187 $ write ptxt "1 RELEASE_NOTES"
/external/skia/relnotes/
DREADME.md7 these files will be inserted into `RELEASE_NOTES.md`, and these files will be
25 Milestones in the top level release notes file (RELEASE_NOTES.md) use a
/external/bazelbuild-rules_testing/.github/workflows/
Drelease.yml43 run: .github/workflows/workspace_snippet.sh ${{ env.GITHUB_REF_NAME }} > release_notes.txt
49 body_path: release_notes.txt
/external/dagger2/util/
Dlatest-dagger-version.sh31 local RELEASE_NOTES=$(echo $RELEASE_JSON | jq '.[0].body')
33 if [ "$RELEASE_NOTES" ]
/external/pigweed/pw_package/py/pw_package/packages/
Dstm32cube.py26 # - For newer releases, the Release_Notes.html file in STM32Cube release, e.g.:
27 # https://github.com/STMicroelectronics/STM32CubeF4/blob/v1.27.1/Release_Notes.html
/external/bazelbuild-rules_rust/.github/
D.gitignore1 release_notes.txt
/external/bazelbuild-rules_rust/.github/workflows/
Drelease.yaml150 …'s#{version}#${{ env.RELEASE_VERSION }}#g' ${{ github.workspace }}/.github/release_notes.template \
152 > ${{ github.workspace }}/.github/release_notes.txt
161 body_path: ${{ github.workspace }}/.github/release_notes.txt
/external/iperf3/docs/
Dnews.rst276 As always, more details can be found in the ``RELEASE_NOTES`` file in
307 ``RELEASE_NOTES`` file in the source distribution.
339 More information on changes can be found in the ``RELEASE_NOTES``
362 More information on changes can be found in the ``RELEASE_NOTES``
D2017-06-06.txt21 There is a mostly-final set of release notes in the RELEASE_NOTES file
Ddev.rst133 1. Update the ``README`` and ``RELEASE_NOTES`` files to be accurate. Make sure
145 vi RELEASE_NOTES # update version number and release date
/external/skia/site/docs/user/release/
D_index.md35 [Skia Graphics Release Notes](https://skia.googlesource.com/skia/+/refs/heads/main/RELEASE_NOTES.md…
/external/bazelbuild-rules_python/.github/workflows/
Drelease.yml44 body_path: release_notes.txt
Dcreate_archive_and_notes.sh27 cat > release_notes.txt << EOF
/external/sdv/vsomeip/third_party/boost/algorithm/string/doc/
Drelease_notes.xml10 <section id="string_algo.release_notes" last-revision="$Date$">
Dstring_algo.xml42 <xi:include href="release_notes.xml"/>
/external/sdv/vsomeip/third_party/boost/phoenix/doc/html/
Dphoenix-doc_HTML.manifest2 phoenix/release_notes.html
/external/pigweed/docs/
Dconf.py260 'docs/release_notes/index': '../../changelog.html',
261 'docs/release_notes/2022_jan': '../../changelog.html',
/external/iperf3/
Diperf3.spec.in49 %%doc README.md INSTALL LICENSE RELEASE_NOTES
/external/pigweed/pw_software_update/
Ddesign.rst43 ├── release_notes.txt
/external/sdv/vsomeip/third_party/boost/proto/doc/
Drelease_notes.qbk8 [section:release_notes Appendix A: Release Notes]
/external/capstone/bindings/python/
Dsetup.py98 src.extend(glob.glob(os.path.join(BUILD_DIR, "RELEASE_NOTES")))

12