| /freebsd/share/doc/IPv6/ |
| H A D | IMPLEMENTATION | 1401 These specifications themselves are fine, however, there can be certain
1516 assume RFC2292 API, the compilation itself goes fine, however, the compiled
1605 sr driver and after that this looks to be working fine. If you need
1850 Tunnel mode works basically fine, but comes with the following restrictions:
|
| /freebsd/contrib/libevent/ |
| H A D | whatsnew-2.0.txt | 315 mingw, or using MSVC (with nmake). Libevent works fine with UNICODE
|
| H A D | whatsnew-2.1.txt | 236 more fine-grained control:
|
| H A D | aclocal.m4 | 76 # source directory, any form will work fine, but in subdirectories a
|
| /freebsd/contrib/kyua/ |
| H A D | NEWS.md | 305 should allow these to run fine.
|
| /freebsd/contrib/ntp/sntp/libevent/ |
| H A D | whatsnew-2.0.txt | 315 mingw, or using MSVC (with nmake). Libevent works fine with UNICODE
|
| H A D | whatsnew-2.1.txt | 236 more fine-grained control:
|
| H A D | aclocal.m4 | 76 # source directory, any form will work fine, but in subdirectories a
|
| /freebsd/crypto/openssl/doc/man1/ |
| H A D | openssl-verification-options.pod | 247 The certificate verification can be fine-tuned with the following flags.
|
| /freebsd/contrib/llvm-project/openmp/runtime/src/i18n/ |
| H A D | en_US.txt | 441 …1$s: granularity=%2$s is not supported with KMP_TOPOLOGY_METHOD=group. Using \"granularity=fine\"."
|
| /freebsd/contrib/googletest/docs/ |
| H A D | gmock_cook_book.md | 215 That's fine as long as the test doesn't need to call it.
1516 perfectly fine to do, can break such tests. Then you have to spend time fixing
1910 Want to do more than one thing when a function is called? That's fine. `DoAll()`
2423 // it's fine to perform this action later, since a copy of the values
3842 It's also fine for the callable to take no arguments, ignoring the arguments
|
| H A D | faq.md | 40 It may seem fine for `TestSuiteName` and `TestName` to contain `_` in the
|
| /freebsd/contrib/bc/manuals/ |
| H A D | build.md | 973 Linux, these tests are usually fine, but on FreeBSD, they are usually a problem.
|
| /freebsd/contrib/googletest/googletest/test/ |
| H A D | googletest-output-test-golden-lin.txt | 122 Just checking that all these values work fine.
|
| /freebsd/libexec/rc/ |
| H A D | network.subr | 1642 # This is fine, do nothing
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/X86/ |
| H A D | X86RegisterInfo.td | 703 // In such cases, it is fine to use RIP as we are sure the 32 high
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/BPF/ |
| H A D | BPFInstrInfo.td | 502 // - it is fine to generate such write when immediate is -1
|
| /freebsd/contrib/sendmail/src/ |
| H A D | README | 912 of services. Some people report that it works fine, others
1248 will work fine. For the resolver you should really port a new
1564 GNU M4 works fine.
|
| /freebsd/contrib/jemalloc/ |
| H A D | ChangeLog | 145 This release is primarily about fine-tuning, ranging from several new features
213 - Add internal fine-grained logging functionality for debugging use.
|
| /freebsd/crypto/heimdal/ |
| H A D | aclocal.m4 | 75 # source directory, any form will work fine, but in subdirectories a
|
| /freebsd/sys/dev/isp/ |
| H A D | DriverManual.txt | 460 is fine on the face of it, but there are some subtle and not so subtle
|
| /freebsd/contrib/openbsm/ |
| H A D | aclocal.m4 | 76 # source directory, any form will work fine, but in subdirectories a
|
| /freebsd/contrib/file/ |
| H A D | aclocal.m4 | 76 # source directory, any form will work fine, but in subdirectories a
|
| /freebsd/contrib/openpam/ |
| H A D | aclocal.m4 | 76 # source directory, any form will work fine, but in subdirectories a
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/ARM/ |
| H A D | ARM.td | 168 // include a generic cycle-counter as well as more fine-grained (often
|