Home
last modified time | relevance | path

Searched refs:release (Results 1 – 25 of 2583) sorted by relevance

12345678910>>...104

/external/curl/
DMakefile.dist98 nmake -f Makefile.$(VC) cfg=release
99 nmake -f Makefile.$(VC) cfg=release-ssl
100 nmake -f Makefile.$(VC) cfg=release-zlib
101 nmake -f Makefile.$(VC) cfg=release-ssl-zlib
102 nmake -f Makefile.$(VC) cfg=release-ssl-dll
103 nmake -f Makefile.$(VC) cfg=release-zlib-dll
104 nmake -f Makefile.$(VC) cfg=release-ssl-dll-zlib-dll
105 nmake -f Makefile.$(VC) cfg=release-dll
106 nmake -f Makefile.$(VC) cfg=release-dll-ssl-dll
107 nmake -f Makefile.$(VC) cfg=release-dll-zlib-dll
[all …]
/external/clang/test/Analysis/
Dproperties.m24 -(oneway void)release; method
109 value = [self.myNumber retain]; // this line fixes the over release
218 [p.name release]; // expected-warning{{not owned}}
221 [p.friend release]; // expected-warning{{not owned}}
226 [friend release]; // expected-warning{{not owned}}
236 [_name release]; // no-warning
240 [other.name release]; // no-warning
249 [name release];
254 [self.name release];
255 [self.name release]; // expected-warning{{not owned}}
[all …]
/external/llvm/docs/
DHowToReleaseLLVM.rst17 If you're looking for the document on how to test the release candidates and
27 The release manager will determine if and when to make a dot release based
35 The release process is roughly as follows:
38 date. Announce release schedule to the LLVM community and update the website.
40 * Create release branch and begin release process.
42 * Send out release candidate sources for first round of testing. Testing lasts
44 fixed. Patches are merged from mainline into the release branch. Also, all
47 release.
49 * Generate and send out the second release candidate sources. Only *critial*
53 * The release notes are updated.
[all …]
DReleaseProcess.rst12 This document contains information about testing the release candidates that will
13 ultimately be the next LLVM release. For more information on how to manage the
14 actual release, please refer to :doc:`HowToReleaseLLVM`.
19 Once the release process starts, the Release Manager will ask for volunteers,
22 * Test and benchmark the previous release
24 * Test and benchmark each release candidate, comparing to the previous release and candidates
28 * Make sure the critical bugs get fixed and merged to the next release candidate
31 should be fixed before the next candidate and what can wait until the next release.
39 * The stage in the release. Less critical bugs should be considered to be fixed between
50 The scripts are in the ``utils/release`` directory.
[all …]
DReleaseNotes.rst9 These are in-progress notes for the upcoming LLVM 3.8 release. You may
17 This document contains the release notes for the LLVM Compiler Infrastructure,
18 release 3.8. Here we describe the status of LLVM, including major improvements
19 from the previous release, improvements in various subprojects of LLVM, and
24 release, please check out the `main LLVM web site <http://llvm.org/>`_. If you
30 LLVM web page, this document applies to the *next* release, not the current
31 one. To see the release notes for a specific release, please see the `releases
34 Non-comprehensive list of changes in this release
36 * With this release, the minimum Windows version required for running LLVM is
40 * With this release, the autoconf build system is deprecated. It will be removed
[all …]
/external/libusb/
DNEWS1 This file lists notable changes in each release. For the full history of all
19 2009-11-06: v1.0.4 release
25 2009-08-27: v1.0.3 release
29 2009-06-13: v1.0.2 release
32 2009-05-12: v1.0.1 release
36 2008-12-13: v1.0.0 release
39 2008-11-21: v0.9.4 release
43 2008-08-23: v0.9.3 release
46 2008-07-19: v0.9.2 release
49 2008-06-28: v0.9.1 release
[all …]
/external/autotest/site_utils/autoupdate/
Drelease.py95 key=lambda (branch, release): self._release_key(release))
99 self._release_key(self._next_build_number_release(release))
100 for (branch, release) in self._sorted_branchpoint_list]
103 def _next_build_number_release(self, release): argument
116 release_components = release.split('.')
121 raise ReleaseError('invalid release number: %s' % release)
129 def _release_key(self, release): argument
144 release_components = release.split('.')
148 raise ReleaseError('invalid release number: %s' % release)
155 return [branch for (branch, release) in self._sorted_branchpoint_list]
[all …]
/external/llvm/utils/release/
Dexport.sh20 release=""
33 release_no_dot=`echo $release | sed -e 's,\.,,g'`
44 $proj-$release$rc.src
47 tar cfJ $proj-$release$rc.src.tar.xz $proj-$release$rc.src
53 -release | --release )
55 release=$1
77 if [ "x$release" = "x" ]; then
Dtag.sh17 release=""
73 -release | --release )
75 release=$1
107 if [ "x$release" = "x" ]; then
114 branch_release=`echo $release | sed -e 's,\([0-9]*\.[0-9]*\).*,\1,' | sed -e 's,\.,,g'`
115 tag_release=`echo $release | sed -e 's,\.,,g'`
/external/valgrind/docs/internals/
Drelease-HOWTO.txt2 TODO list when doing a Valgrind release (with release number "X.Y.Z")
14 - Tell valgrind-developers you want to do a release. Give a timeframe for
16 release.
21 release date probably won't be known yet, updating it is in the list below
22 of tasks for the official release.)
25 for the release. (include/valgrind.h)
27 - Write release notes, add to NEWS. Include a list of fixed bugs from
37 at the previous release. Work backwards through this list until
43 Suggestion for next release: when a bug is fixed, update NEWS
63 For each release candidate (should do release candidates for feature
[all …]
/external/libusb-compat/
DNEWS1 This file lists notable changes in each release. For the full history of all
4 2009-07-09: libusb-compat-0.1.3 release
8 2009-06-11: libusb-compat-0.1.2 release
11 2009-05-28: libusb-compat-0.1.1 release
14 2008-12-13: libusb-compat-0.1.0 release
17 2008-11-21: libusb-compat-0.1.0-beta3 release
20 2008-06-28: libusb-compat-0.1.0-beta2 release
24 2008-05-25: libusb-compat-0.1.0-beta1 release
25 * Initial beta release
/external/clang/test/ARCMT/
Dreleases.m14 - (oneway void)release; method
36 [x release];
38 [IhaveSideEffect() release];
40 [x release], x = 0;
44 [x release];
51 [p release];
52 (([p release]));
62 [_foo release];
71 [p release];
80 #define RELEASE_MACRO(x) [x release]
[all …]
Dreleases-driver.m14 - (oneway void)release; method
36 [x release];
38 [IhaveSideEffect() release];
40 [x release], x = 0;
46 [p release];
47 (([p release]));
57 [_foo release];
61 #define RELEASE_MACRO(x) [x release]
/external/elfutils/libdwfl/
Dlinux-kernel-modules.c147 if (utsname.release[0] == '\0' && uname (&utsname) != 0) in kernel_release()
149 return utsname.release; in kernel_release()
153 find_kernel_elf (Dwfl *dwfl, const char *release, char **fname) in find_kernel_elf() argument
155 if ((release[0] == '/' in find_kernel_elf()
156 ? asprintf (fname, "%s/vmlinux", release) in find_kernel_elf()
157 : asprintf (fname, "/boot/vmlinux-%s", release)) < 0) in find_kernel_elf()
161 if (fd < 0 && release[0] != '/') in find_kernel_elf()
164 if (asprintf (fname, MODULEDIRFMT "/vmlinux", release) < 0) in find_kernel_elf()
173 get_release (Dwfl *dwfl, const char **release) in get_release() argument
178 const char *release_string = release == NULL ? NULL : *release; in get_release()
[all …]
/external/opencv3/samples/gpu/
Dstereo_multi.cpp148 d_leftFrame.release(); in ~StereoSingleGpu()
149 d_rightFrame.release(); in ~StereoSingleGpu()
150 d_disparity.release(); in ~StereoSingleGpu()
151 d_alg.release(); in ~StereoSingleGpu()
208 d_leftFrames[0].release(); in ~StereoMultiGpuThread()
209 d_rightFrames[0].release(); in ~StereoMultiGpuThread()
210 d_disparities[0].release(); in ~StereoMultiGpuThread()
211 d_algs[0].release(); in ~StereoMultiGpuThread()
214 d_leftFrames[1].release(); in ~StereoMultiGpuThread()
215 d_rightFrames[1].release(); in ~StereoMultiGpuThread()
[all …]
/external/opencv3/modules/java/android_test/src/org/opencv/test/
DOpenCVTestCase.java149 gray0.release(); in tearDown()
150 gray1.release(); in tearDown()
151 gray2.release(); in tearDown()
152 gray3.release(); in tearDown()
153 gray9.release(); in tearDown()
154 gray127.release(); in tearDown()
155 gray128.release(); in tearDown()
156 gray255.release(); in tearDown()
157 gray_16u_256.release(); in tearDown()
158 gray_16s_1024.release(); in tearDown()
[all …]
/external/chromium-trace/catapult/third_party/gsutil/third_party/python-gflags/debian/
Dchangelog3 * New upstream release.
9 * New upstream release.
15 * New upstream release.
21 * New upstream release.
27 * New upstream release (fixes manifest and setup.py files)
33 * New upstream release.
39 * New upstream release.
51 * Initial release.
/external/antlr/antlr-3.4/runtime/ObjC/Framework/examples/treerewrite/
Dmain.m27 [lexer release];
28 [stream release];
29 [tokenStream release];
30 [parser release];
31 // [treeStream release];
32 // [walker release];
34 [pool release];
/external/replicaisland/src/com/replica/replicaisland/
DDrawableFactory.java56 public void release(DrawableObject object) { in release() method in DrawableFactory
59 pool.release(object); in release()
85 public void release(Object entry) { in release() method in DrawableFactory.DrawableBitmapPool
87 super.release(entry); in release()
122 public void release(Object entry) { in release() method in DrawableFactory.ScrollableBitmapPool
124 super.release(entry); in release()
151 public void release(Object entry) { in release() method in DrawableFactory.TiledBackgroundVertexGridPool
154 super.release(entry); in release()
/external/opencv3/modules/java/pure_test/src/org/opencv/test/
DOpenCVTestCase.java179 gray0.release(); in tearDown()
180 gray1.release(); in tearDown()
181 gray2.release(); in tearDown()
182 gray3.release(); in tearDown()
183 gray9.release(); in tearDown()
184 gray127.release(); in tearDown()
185 gray128.release(); in tearDown()
186 gray255.release(); in tearDown()
187 gray_16u_256.release(); in tearDown()
188 gray_16s_1024.release(); in tearDown()
[all …]
/external/apache-http/src/org/apache/http/util/
DVersionInfo.java102 String release, String time, String clsldr) { in VersionInfo() argument
110 infoRelease = (release != null) ? release : UNAVAILABLE; in VersionInfo()
294 String release = null; in fromMap() local
302 release = (String) info.get(PROPERTY_RELEASE); in fromMap()
303 if ((release != null) && ((release.length() < 1) || in fromMap()
304 (release.equals("${pom.version}")))) in fromMap()
305 release = null; in fromMap()
319 return new VersionInfo(pckg, module, release, timestamp, clsldrstr); in fromMap()
/external/curl/docs/
DRELEASE-PROCEDURE1 curl release procedure - how to do a release
16 - run "./maketgz 7.34.0" to build the release tarballs. It is important that
32 - edit `_newslog.html` (announce the new release) and
55 curl release scheduling
62 insert releases outside of the schedule or we can move the release date - but
65 Each 8 week release cycle is split in two 4-week periods.
67 - During the first 4 weeks after a release, we allow new features and changes
69 used for the next release.
73 release.
78 Based on the description above, here are some planned release dates (at the
/external/curl/packages/Solaris/
DMakefile.am15 if [ ! -f release ]; then echo 0 > release; fi
16 if [ `find root -newer release -print|wc -l` -gt 0 ]; then expr `cat release` + 1 > release; fi
25 echo VERSION=`cat ./release` >> pkginfo
/external/bison/
DREADME-release1 Here are most of the steps we (maintainers) follow when making a release.
18 * Ensure that you've pushed all changes that belong in the release:
30 * Pre-release testing: ensure that the following command succeeds:
34 * To (i) set the date, version number, and release TYPE on line 3 of
35 NEWS, (ii) commit that, and (iii) tag the release, run
38 make release-commit RELEASE='X.Y TYPE'
40 * Run the following to create release tarballs. Your choice selects the
45 make release RELEASE='X.Y TYPE'
50 * While that's happening, write the release announcement that you will
56 * Run the gnupload command that was suggested by your "make release"
[all …]
/external/libdrm/
DRELEASING1 The release criteria for libdrm is essentially "if you need a release,
2 make one". There is no designated release engineer or maintainer.
3 Anybody is free to make a release if there's a certain feature or bug
7 support to libdrm, at which point we typically create a new release.
10 Follow these steps to release a new version of libdrm:
23 4) (optional step, release.sh will make distcheck for you, but it can be
40 commit with the version number of the release as the name and a
41 message of "libdrm X.Y.Z". For example, for the 2.4.16 release
52 7) Use the release.sh script from the xorg/util/modular repo to
58 ./modular/release.sh libdrm
[all …]

12345678910>>...104