/freebsd/contrib/ntp/ntpsnmpd/ |
H A D | ntpsnmpd.1ntpsnmpdmdoc | 107 libopts had an internal operational error. Please report 116 Please send bug reports to: https://bugs.ntp.org, bugs@ntp.org 122 please fill me in... 124 please fill me in... 126 please fill me in... 128 please fill me in... 130 please fill me in... 132 please fill me in... 134 please fill me in... 136 please fil [all...] |
H A D | ntpsnmpd.mdoc.in | 107 libopts had an internal operational error. Please report 116 Please send bug reports to: https://bugs.ntp.org, bugs@ntp.org 122 please fill me in... 124 please fill me in... 126 please fill me in... 128 please fill me in... 130 please fill me in... 132 please fill me in... 134 please fill me in... 136 please fil [all...] |
H A D | ntpsnmpd.man.in | 134 libopts had an internal operational error. Please report 144 Please send bug reports to: https://bugs.ntp.org, bugs@ntp.org 152 please fill me in... 157 please fill me in... 162 please fill me in... 167 please fill me in... 172 please fill me in... 177 please fill me in... 182 please fill me in... 187 please fil [all...] |
H A D | ntpsnmpd.1ntpsnmpdman | 134 libopts had an internal operational error. Please report 144 Please send bug reports to: https://bugs.ntp.org, bugs@ntp.org 152 please fill me in... 157 please fill me in... 162 please fill me in... 167 please fill me in... 172 please fill me in... 177 please fill me in... 182 please fill me in... 187 please fil [all...] |
H A D | ntpsnmpd-opts.def | 92 please fill me in... 94 please fill me in... 96 please fill me in... 98 please fill me in... 100 please fill me in... 102 please fill me in... 104 please fill me in... 106 please fill me in... 108 please fill me in... 110 please fill me in...
|
/freebsd/ |
H A D | CONTRIBUTING.md | 5 Please read the guidelines in [Contributing to FreeBSD](https://docs.freebsd.org/en/articles/contri… 21 A change should be submitted by only one method. For example, please do not 42 …nge during review. If the review suggests changes that expand the scope, please create an independ… 48 * If the commit fixes a bug, please add 'PR: \<bugnumber\>' to the commit message. 49 * If there's a code review in Phabricator, please include a link as a 'Differential Revision: ' lin… 50 …rough a static analysis tool, please don't submit the raw results. Please also see the chunking up… 52 When updating your pull request, please rebase with a forced push rather than a 57 the community, or need extensive revision. Please avoid creating large, 62 Please make sure that your submissions compile and work before submitting. If 67 other commit, please go ahead and prepare those patches. However, please avoid just [all …]
|
/freebsd/contrib/llvm-project/libcxx/modules/ |
H A D | std.compat.cppm.in | 58 # error "please update the header information for <debugging> in headers_not_available in utils/… 61 # error "please update the header information for <flat_map> in headers_not_available in utils/l… 64 # error "please update the header information for <flat_set> in headers_not_available in utils/l… 67 # error "please update the header information for <generator> in headers_not_available in utils/… 70 # error "please update the header information for <hazard_pointer> in headers_not_available in u… 73 # error "please update the header information for <inplace_vector> in headers_not_available in u… 76 # error "please update the header information for <linalg> in headers_not_available in utils/lib… 79 # error "please update the header information for <rcu> in headers_not_available in utils/libcxx… 82 # error "please update the header information for <spanstream> in headers_not_available in utils… 85 # error "please update the header information for <stacktrace> in headers_not_available in utils… [all …]
|
H A D | std.cppm.in | 180 # error "please update the header information for <debugging> in headers_not_available in utils/… 183 # error "please update the header information for <flat_map> in headers_not_available in utils/l… 186 # error "please update the header information for <flat_set> in headers_not_available in utils/l… 189 # error "please update the header information for <generator> in headers_not_available in utils/… 192 # error "please update the header information for <hazard_pointer> in headers_not_available in u… 195 # error "please update the header information for <inplace_vector> in headers_not_available in u… 198 # error "please update the header information for <linalg> in headers_not_available in utils/lib… 201 # error "please update the header information for <rcu> in headers_not_available in utils/libcxx… 204 # error "please update the header information for <spanstream> in headers_not_available in utils… 207 # error "please update the header information for <stacktrace> in headers_not_available in utils… [all …]
|
/freebsd/contrib/diff/ |
H A D | README | 7 Please see the file COPYING for copying conditions. 9 Please see the file doc/version.texi for version information. 11 Please see the file doc/diff.texi (or doc/diff.info) for documentation 16 Please see the file ABOUT-NLS for notes about translations. 18 Please see the file INSTALL for generic compilation and installation 29 installation. If you have an older version of libiconv, please 31 the problem seems isolated to diffutils, though, please report a bug. 34 have a nonstandard compiler, please install GCC first. 47 Please report bugs to <bug-gnu-utils@gnu.org>.
|
/freebsd/usr.sbin/bsdconfig/include/ |
H A D | messages.subr | 73 msg_cant_start_wpa_supplicant="Can't start wpa_supplicant(8). Please create a wlan(4)\ninterface fr… 135 msg_failed_to_add_default_route="Failed to add a default route; please check your network configura… 161 …t="WARNING: hostname variable not set and is a non-optional\nparameter. Please add this to your i… 246 msg_no_cd_dvd_devices_found="No CD/DVD devices found! Please check that your system's\nconfigurati… 282 msg_please_enter_password="Please enter your password for sudo(8):" 283 msg_please_enter_the_address_of_the_http_proxy="Please enter the address of the HTTP proxy in this … 284 msg_please_enter_the_full_nfs_file_specification="Please enter the full NFS file specification for … 285 msg_please_enter_the_password_for_this_user="Please enter the password for this user:" 286 msg_please_enter_the_username_you_wish_to_login_as="Please enter the username you wish to login as:" 287 msg_please_enter_username_password="Please enter a username and password for sudo(8):" [all …]
|
/freebsd/usr.sbin/bsdconfig/networking/include/ |
H A D | messages.subr | 80 msg_please_enter_default_router="Please enter the IP address of your default\nrouter/gateway. The … 81 msg_please_enter_fqhn="Please enter your fully qualified hostname (e.g. full.example.com). The\ndom… 82 msg_please_enter_mediaopts="Please enter additional network media options to be passed to ifconfig(… 83 msg_please_enter_nameserver="Please enter the new IP address of the DNS nameserver:" 84 msg_please_enter_nameserver_existing="Please enter the new IP address of the DNS nameserver\n(set t… 85 msg_please_enter_new_ip_addr="Please enter the new IP address of the %s interface:" 86 msg_please_enter_subnet_mask="Please enter the new network subnet mask for the %s interface:" 89 …le_editing="ERROR! resolv.conf(5) has changed while editing this\nvalue. Please try again after wa… 90 …R! The entry you are trying to edit no longer\nexists in resolv.conf(5). Please try again after\nw… 100 …ptions="Below is a list of supported media options for the %s interface. Please select the options… [all …]
|
/freebsd/contrib/libpcap/ |
H A D | CONTRIBUTING.md | 5 code execution etc) please send an e-mail to security@tcpdump.org, do not use 9 properly, missing support for a network interface type or DLT) please check 11 please check that the problem reproduces with the current git master branch of 13 above), please navigate to https://github.com/the-tcpdump-group/libpcap/issues 14 and check if the problem has already been reported. If it has not, please open 24 Please note that if you know exactly how to solve the problem and the solution
|
/freebsd/contrib/googletest/.github/ISSUE_TEMPLATE/ |
H A D | 00-bug_report.yml | 3 title: "[Bug]: Please title this bug report" 16 …ant that we are able to reproduce the problem that you are experiencing. Please provide all code a… 23 …description: Please include the output of `git rev-parse HEAD` or the GoogleTest release version n… 30 …description: If you are using a Linux distribution please include the name and version of the dist… 37 …description: Please include the output of `gcc -v` or `clang -v`, or the equivalent for your compi… 44 …description: Please include the output of `bazel --version` or `cmake --version`, or the equivalen…
|
/freebsd/sys/dev/isci/scil/ |
H A D | scif_sas_design.h | 88 Please refer to Base Design specification for further information. 104 the remaining source file (e.g. scif_sas_controller.c). As a result, please 143 For more information on each object appearing in the diagram, please 156 associated with this object. Please reference these files directly for 171 associated with this object. Please reference these files directly for 188 methods, members, etc. associated with this object. Please reference 209 classes (common files). Please reference these files directly for further 226 super-state machine please refer to SCI_BASE_REMOTE_DEVICE_STATES 235 For more information on the starting sub-state machine states please refer 247 For more information on the ready sub-state machine states please refer [all …]
|
H A D | intel_sas.h | 91 * individual fields please reference the SAS specification 122 * individual fields please reference the SAS specification 152 * on each of these individual fields please reference the SAS 255 * individual fields please reference the SAS specification SSP 279 * please reference the SAS specification SSP transport layer 307 * individual fields please reference the SAS specification SSP 342 * specific information on the individual fields please reference 381 * individual fields please reference the SAS specification. 395 * individual fields please reference the SAS specification Link 411 * individual fields please reference the SAS specification. [all …]
|
/freebsd/contrib/tzcode/ |
H A D | CONTRIBUTING | 3 Please do not create issues or pull requests on GitHub, as the 11 free to fill gaps or fix mistakes, and please email improvements 12 to <tz@iana.org> for use in the future. In your email, please give 17 To email small changes, please run a POSIX shell command like 22 such as renaming, adding or removing zones, please read 31 For changes that fix sensitive security-related bugs, please see the 34 Please submit changes against either the latest release
|
/freebsd/contrib/tzdata/ |
H A D | CONTRIBUTING | 3 Please do not create issues or pull requests on GitHub, as the 11 free to fill gaps or fix mistakes, and please email improvements 12 to <tz@iana.org> for use in the future. In your email, please give 17 To email small changes, please run a POSIX shell command like 22 such as renaming, adding or removing zones, please read 31 For changes that fix sensitive security-related bugs, please see the 34 Please submit changes against either the latest release
|
/freebsd/crypto/openssl/ |
H A D | CONTRIBUTING.md | 4 Please visit our [Getting Started] page for other ideas about how to contribute. 13 please open an [issue on GitHub](https://github.com/openssl/openssl/issues). 15 To submit a patch or implement a new feature, please open a 22 To make it easier to review and accept your pull request, please follow these 84 either be added to an existing test, or completely new. Please see 88 documentation. Please look at the `.pod` files in `doc/man[1357]` for 97 Please note that this is NOT simply a copy of git-log one-liners. 104 security fixes, please add a line in [NEWS.md](NEWS.md).
|
/freebsd/contrib/ntp/html/ |
H A D | bugs.html | 20 …rogram bug in this distribution, please send a report to <a href="mailto:security@ntp.org">securit… 22 …please send a report to the NTP Public Service Project Bug Tracking System (Bugzilla) at <a href="… 23 …please remember that your report will be held until one of our volunteers enters it in Bugzilla. T…
|
/freebsd/contrib/one-true-awk/ |
H A D | README.md | 63 in `FIXES`. If you distribute this code further, please please please 66 If you find errors, please report them 68 Please _also_ open an issue in the GitHub issue tracker, to make 76 * Please do not use functions or facilities that are not standard (e.g., 79 * Please run the test suite and make sure that your changes pass before 86 * Please create the pull request with a request
|
/freebsd/contrib/unbound/contrib/android/ |
H A D | setenv_android.sh | 17 echo "ANDROID_API is not set. Please set it" 22 echo "ANDROID_CPU is not set. Please set it" 27 echo "ERROR: ANDROID_NDK_ROOT is not a valid path. Please set it." 56 echo "ERROR: ANDROID_TOOLCHAIN is not a valid path. Please set it." 63 echo "ERROR: ANDROID_SYSROOT is not a valid path. Please set it." 136 echo "ERROR: Failed to find Android clang. Please edit this script." 142 echo "ERROR: Failed to find Android clang++. Please edit this script." 148 echo "ERROR: Failed to find Android ranlib. Please edit this script." 154 echo "ERROR: Failed to find Android ar. Please edit this script." 160 echo "ERROR: Failed to find Android as. Please edit this script." [all …]
|
/freebsd/crypto/openssh/ |
H A D | README | 4 Please read https://www.openssh.com/report.html for bug reporting 30 There is now several mailing lists for this port of OpenSSH. Please 33 Please send bug reports and patches to https://bugzilla.mindrot.org or 36 are welcomed, but please follow the OpenBSD style guidelines[1]. 38 Please refer to the INSTALL document for information on dependencies and
|
/freebsd/sys/contrib/openzfs/.github/ |
H A D | CONTRIBUTING.md | 63 or IRC are the best places to ask for help. Please do not file 69 *Please* contact us via the [zfs-discuss mailing 73 If you run into an issue, please search our [issue 81 #### When opening a new issue, please include the following information at the top of the issue: 131 * Please attempt to limit pull requests to a single commit which resolves 155 ), please run `make checkstyle` and resolve any warnings. 158 * If your pull request improves performance, please include some benchmarks. 210 please summarize important information such as why the proposed 221 Please provide at least a couple sentences describing the 222 change. If necessary, please summarize decisions such as [all …]
|
H A D | PULL_REQUEST_TEMPLATE.md | 1 <!--- Please fill out the following template, which will help other contributors review your Pull R… 12 <!--- If it fixes an open issue, please link to the issue here. --> 18 <!--- Please describe in detail how you tested your changes. --> 21 <!--- If your change is a performance enhancement, please provide benchmarks here. --> 22 <!--- Please think about using the draft PR feature if appropriate -->
|
/freebsd/sys/contrib/openzfs/.github/ISSUE_TEMPLATE/ |
H A D | bug_report.md | 10 <!-- Please fill out the following template, which will help other contributors address your issue.… 15 *IMPORTANT* - Please check our issue tracker before opening a new issue. 19 Please fill in as much of the template as possible. 46 *IMPORTANT* - Please mark logs and text output from terminal commands
|