| /netbsd-src/crypto/external/bsd/openssl.old/dist/crypto/asn1/ |
| H A D | a_strnid.c | 15 static STACK_OF(ASN1_STRING_TABLE) *stable = NULL; 133 if (stable) { in ASN1_STRING_TABLE_get() 134 idx = sk_ASN1_STRING_TABLE_find(stable, &fnd); in ASN1_STRING_TABLE_get() 136 return sk_ASN1_STRING_TABLE_value(stable, idx); in ASN1_STRING_TABLE_get() 151 if (stable == NULL) { in stable_get() 152 stable = sk_ASN1_STRING_TABLE_new(sk_table_cmp); in stable_get() 153 if (stable == NULL) in stable_get() 163 if (!sk_ASN1_STRING_TABLE_push(stable, rv)) { in stable_get() 208 tmp = stable; in ASN1_STRING_TABLE_cleanup() 211 stable = NULL; in ASN1_STRING_TABLE_cleanup()
|
| /netbsd-src/crypto/external/bsd/openssl/dist/crypto/asn1/ |
| H A D | a_strnid.c | 15 static STACK_OF(ASN1_STRING_TABLE) *stable = NULL; 138 if (stable) { in ASN1_STRING_TABLE_get() 139 idx = sk_ASN1_STRING_TABLE_find(stable, &fnd); in ASN1_STRING_TABLE_get() 141 return sk_ASN1_STRING_TABLE_value(stable, idx); in ASN1_STRING_TABLE_get() 156 if (stable == NULL) { in stable_get() 157 stable = sk_ASN1_STRING_TABLE_new(sk_table_cmp); in stable_get() 158 if (stable == NULL) in stable_get() 168 if (!sk_ASN1_STRING_TABLE_push(stable, rv)) { in stable_get() 213 tmp = stable; in ASN1_STRING_TABLE_cleanup() 216 stable = NULL; in ASN1_STRING_TABLE_cleanup()
|
| /netbsd-src/external/bsd/ntp/dist/ |
| H A D | README.patches | 7 If you are going to patch both ntp-stable and ntp-dev 10 > cd ntp-stable 11 > (make and test your changes to ntp-stable first) 12 > (commit your changes to ntp-stable) 14 > bk pull ../ntp-stable (get your changes from ntp-stable) 19 from ntp-stable to ntp-dev than it is to move changes from ntp-dev to 20 ntp-stable. 35 patches for both ntp-stable and ntp-dev.
|
| H A D | README.pullrequests | 5 There are two branches, master and stable. 7 The stable branch is the current supported production code branch, the 8 ntp-stable code (even 2nd number). 15 on the stable branch, and pull your work into a master copy to allow for 19 current stable release (the ntp-stable code) then it's better to do your 22 Make sure that any changes you make to stable pull cleanly into master. 24 It's possible that after pulling your changes from stable to master that 28 master or for master+stable, it will be easy for us to evaluate and
|
| H A D | README.versions | 8 C is the minor release number. Even numbers are 'stable' releases and 18 4.2.2 A production release (from the ntp-stable repository) 19 4.2.2p2 A production release (from the ntp-stable repository) 24 be copied into the ntp-stable and the cycle will repeat.
|
| /netbsd-src/external/bsd/ntp/dist/scripts/build/ |
| H A D | UpdatePoint | 28 dev|stable) 67 stable) 75 stable) 127 stable) 242 stable::1::) 281 stable)
|
| H A D | VersionName | 32 stable::[1-9]* | dev::[0-9]*) 56 beta::stable) 62 rc::stable|RC::stable)
|
| H A D | checkChangeLog | 10 stable) ;; 23 stable---) 25 stable*)
|
| /netbsd-src/external/cddl/dtracetoolkit/dist/Notes/ |
| H A D | ALLfbt_notes.txt | 22 they would all use stable providers such as "proc", "sched", "io", etc. 27 * Not all stable providers exist yet. Many are in development, such as 28 stable networking providers. 37 in a very unstable way, as a temporary solution while stable providers 39 * Once stable providers exist, "fbt" scripts can be rewritten to use them; 41 the stable providers. (in other words, this won't help you if you remain 47 to be stable nor should it ever be (to do so would freeze kernel development 49 integration of stable providers (although that doesn't help people who keep 74 in a stable way, it may help to raise that with your vendor (Sun for Solaris,
|
| /netbsd-src/external/cddl/dtracetoolkit/dist/Docs/Notes/ |
| H A D | ALLfbt_notes.txt | 22 they would all use stable providers such as "proc", "sched", "io", etc. 27 * Not all stable providers exist yet. Many are in development, such as 28 stable networking providers. 37 in a very unstable way, as a temporary solution while stable providers 39 * Once stable providers exist, "fbt" scripts can be rewritten to use them; 41 the stable providers. (in other words, this won't help you if you remain 47 to be stable nor should it ever be (to do so would freeze kernel development 49 integration of stable providers (although that doesn't help people who keep 74 in a stable way, it may help to raise that with your vendor (Sun for Solaris,
|
| /netbsd-src/external/bsd/am-utils/dist/ |
| H A D | cvs-server.txt | 15 Or, to checkout the stable branch: 17 $ cvs -d ${USER}@cvs.am-utils.org:/home/cvsroot checkout -r amd-6-1-stable am-utils 21 $ cvs -d ${USER}@cvs.am-utils.org:/home/cvsroot checkout -r amd-6-0-stable am-utils 29 To merge changes from the stable branch into the main (development) branch: 31 $ cvs update -j amd-6-1-stable -kk
|
| /netbsd-src/usr.sbin/mrouted/ |
| H A D | prune.h | 36 struct stable *gt_srctbl; /* source table */ 49 struct stable struct 51 struct stable *st_next; /* pointer to the next entry */ argument
|
| H A D | prune.c | 363 struct stable *st; in update_kernel() 398 struct stable * 401 struct stable *st; in find_grp_src() 420 next_grp_src_mask(struct gtable **gtpp, struct stable **stpp, u_long grp, in next_grp_src_mask() 424 struct stable *st, *sbest = NULL; in next_grp_src_mask() 466 refresh_sg(struct sioc_sg_req *sg, struct gtable *gt, struct stable *st) in refresh_sg() 550 next_child(struct gtable **gtpp, struct stable **stpp, u_long grp, u_long src, in next_child() 553 struct stable *st; in next_child() 594 struct stable *st,**stnp; in add_table_entry() 707 st = (struct stable *)malloc(sizeof(struct stable)); in add_table_entry() [all …]
|
| /netbsd-src/external/gpl3/gcc.old/dist/libphobos/src/std/algorithm/ |
| H A D | mutation.d | 1669 stable, 1678 assert(remove!(SwapStrategy.stable)(a, 1) == [0, 2, 3]); 1690 assert(partition!(a => a > 3, SwapStrategy.stable)(arr) == [1, 2, 3]); 1797 (SwapStrategy s = SwapStrategy.stable, Range, Offset...) 1799 if (s != SwapStrategy.stable 1884 (SwapStrategy s = SwapStrategy.stable, Range, Offset...) 1886 if (s == SwapStrategy.stable 1939 assert(remove!(SwapStrategy.stable)(a, 1) == [ 0, 2, 3, 4, 5 ]); 1941 assert(remove!(SwapStrategy.stable)(a, 1, 3) == [ 0, 2, 4, 5] ); 1943 assert(remove!(SwapStrategy.stable)(a, 1, tuple(3, 6)) == [ 0, 2 ]); [all …]
|
| /netbsd-src/external/gpl3/gcc/dist/libphobos/src/std/algorithm/ |
| H A D | mutation.d | 1763 stable, 1770 assert(remove!(SwapStrategy.stable)(a, 1) == [0, 2, 3]); 1782 assert(partition!(a => a > 3, SwapStrategy.stable)(arr) == [1, 2, 3]); 1920 (SwapStrategy s = SwapStrategy.stable, Range, Offset ...) 1948 (SwapStrategy s = SwapStrategy.stable, Range, Offset ...) 1961 assert(remove!(SwapStrategy.stable)(a, 1) == [ 0, 2, 3, 4, 5 ]); 1963 assert(remove!(SwapStrategy.stable)(a, 1, 3) == [ 0, 2, 4, 5] ); 1965 assert(remove!(SwapStrategy.stable)(a, 1, tuple(3, 6)) == [ 0, 2 ]); 1994 assert([5, 6, 7, 8].remove!(SwapStrategy.stable)(1) == [5, 7, 8]); 2004 static assert(s == SwapStrategy.stable, [all …]
|
| /netbsd-src/external/bsd/ntp/dist/scripts/rc/ |
| H A D | README | 4 any services require stable system clock, the ntpwait script should be run 8 NetBSD). If a service requires stable system time, indicate it with TIMESYNC
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/ |
| H A D | sort.cc | 258 bool stable = (ssize_t) size < 0; in gcc_qsort() local 259 if (stable) in gcc_qsort() 281 bool stable = (ssize_t) size < 0; in gcc_sort_r() local 282 if (stable) in gcc_sort_r()
|
| /netbsd-src/external/ibm-public/postfix/dist/ |
| H A D | RELEASE_NOTES-3.3 | 1 This is the Postfix 3.3 (stable) release. 3 The stable Postfix release is called postfix-3.3.x where 3=major 4 release number, 3=minor release number, x=patchlevel. The stable 14 specifies the release date of a stable release or snapshot release.
|
| H A D | RELEASE_NOTES-3.5 | 1 This is the Postfix 3.5 (stable) release. 3 The stable Postfix release is called postfix-3.5.x where 3=major 4 release number, 5=minor release number, x=patchlevel. The stable 14 specifies the release date of a stable release or snapshot release.
|
| H A D | RELEASE_NOTES-3.2 | 1 This is the Postfix 3.2 (stable) release. 3 The stable Postfix release is called postfix-3.2.x where 3=major 4 release number, 2=minor release number, x=patchlevel. The stable 14 specifies the release date of a stable release or snapshot release.
|
| H A D | RELEASE_NOTES | 1 This is the Postfix 3.8 stable release. 3 The stable Postfix release is called postfix-3.8.x where 3=major 4 release number, 8=minor release number, x=patchlevel. The stable 14 specifies the release date of a stable release or snapshot release.
|
| /netbsd-src/external/apache2/llvm/dist/clang/docs/ |
| H A D | Tooling.rst | 12 `LibClang <https://clang.llvm.org/doxygen/group__CINDEX.html>`_ is a stable high 25 * need a stable interface that takes care to be backwards compatible 80 * want a stable interface so you don't need to change your code when the AST API
|
| /netbsd-src/external/bsd/ntp/dist/scripts/ntp-wait/ |
| H A D | ntp-wait-opts.def | 35 of @code{ntpd} that returns "the time is not yet stable". 65 has not yet produced a synchronized and stable system clock.
|
| /netbsd-src/external/mit/libuv/dist/ |
| H A D | CONTRIBUTING.md | 19 or the stable branch. As a rule of thumb, bug fixes go into the stable branch 22 The stable branch is effectively frozen; patches that change the libuv 42 (Where v1.x is the latest stable branch as of this writing.)
|
| /netbsd-src/external/ibm-public/postfix/dist/README_FILES/ |
| H A D | RELEASE_NOTES | 1 This is the Postfix 3.8 stable release. 3 The stable Postfix release is called postfix-3.8.x where 3=major 4 release number, 8=minor release number, x=patchlevel. The stable 14 specifies the release date of a stable release or snapshot release.
|