/openbsd-src/gnu/llvm/lldb/docs/ |
H A D | doxygen.cfg.in | 6 # All text after a hash (#) is considered a comment and will be ignored 37 # base path where the generated documentation will be put. 38 # If a relative path is entered, it will be relative to the location 39 # where doxygen was started. If left blank the current directory will be used. 43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 45 # format and will distribute the generated files over these directories. 53 # documentation generated by doxygen is written. Doxygen will use this 65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 72 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 75 # brief descriptions will be completely suppressed. [all …]
|
/openbsd-src/gnu/lib/libstdc++/libstdc++/docs/doxygen/ |
H A D | user.cfg.in | 6 # All text after a hash (#) is considered a comment and will be ignored 36 # base path where the generated documentation will be put. 37 # If a relative path is entered, it will be relative to the location 38 # where doxygen was started. If left blank the current directory will be used. 43 # documentation generated by doxygen is written. Doxygen will use this 53 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 55 # Private class members and static file members will be hidden unless 61 # will be included in the documentation. 66 # will be included in the documentation. 71 # defined locally in source files will be included in the documentation. [all …]
|
/openbsd-src/gnu/gcc/libstdc++-v3/docs/doxygen/ |
H A D | user.cfg.in | 6 # All text after a hash (#) is considered a comment and will be ignored 29 # base path where the generated documentation will be put. 30 # If a relative path is entered, it will be relative to the location 31 # where doxygen was started. If left blank the current directory will be used. 35 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 37 # format and will distribute the generated files over these directories. 45 # documentation generated by doxygen is written. Doxygen will use this 67 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 74 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will 77 # BRIEF_MEMBER_DESC are set to NO, the brief descriptions will be [all …]
|
/openbsd-src/gnu/gcc/libstdc++-v3/include/ext/pb_ds/ |
H A D | assoc_container.hpp | 11 // This library is distributed in the hope that it will be useful, but 184 // Constructor taking some policy objects. r_hash_fn will be 189 // Constructor taking some policy objects. r_hash_fn will be 191 // r_eq_fn will be copied by the eq_fn object of the container 196 // Constructor taking some policy objects. r_hash_fn will be 198 // will be copied by the eq_fn object of the container object, and 199 // r_comb_hash_fn will be copied by the comb_hash_fn object of the 204 // Constructor taking some policy objects. r_hash_fn will be 206 // will be copied by the eq_fn object of the container object, 207 // r_comb_hash_fn will be copied by the comb_hash_fn object of the [all …]
|
/openbsd-src/usr.bin/lex/ |
H A D | ChangeLog | 5 2014-02-14 Will Estes <westes575@gmail.com> 13 2014-02-14 Will Estes <westes575@gmail.com> 21 2014-02-14 Will Estes <westes575@gmail.com> 29 2014-02-14 Will Estes <westes575@gmail.com> 37 2014-02-14 Will Estes <westes575@gmail.com> 45 2014-02-14 Will Estes <westes575@gmail.com> 53 2014-02-14 Will Estes <westes575@gmail.com> 61 2014-02-14 Will Estes <westes575@gmail.com> 69 2014-02-14 Will Estes <westes575@gmail.com> 74 2014-02-14 Will Estes <westes575@gmail.com> [all …]
|
/openbsd-src/gnu/llvm/llvm/docs/ |
H A D | doxygen.cfg.in | 9 # All text after a single hash (#) is considered a comment and will be ignored. 51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo 57 # into which the generated documentation will be written. If a relative path is 58 # entered, it will be relative to the location where doxygen was started. If 59 # left blank the current directory will be used. 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 65 # will distribute the generated files over these directories. Enabling this 74 # documentation generated by doxygen is written. Doxygen will use this 88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 95 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief [all …]
|
H A D | ResponseGuide.rst | 11 All responses to Code of Conduct reports will be managed by a Code of Conduct 17 In-person events will have an additional response team to immediately respond 21 * For LLVM meetups, the local organizers will be the first point of contact. 23 will have a code of conduct response team or point of contact for CoC 41 will be taken. Specific guidance is in the checklist below. 88 4. During this process, the :ref:`reporter will be informed of the 100 The committee will never make public statements about a resolution and will 102 statement is necessary and requested by the committee, it will be given by the 108 When a report is received, the committee will reply to the reporter to confirm 111 This acknowledgement will contain: [all …]
|
/openbsd-src/gnu/llvm/clang/docs/ |
H A D | doxygen.cfg.in | 9 # All text after a single hash (#) is considered a comment and will be ignored. 51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo 57 # into which the generated documentation will be written. If a relative path is 58 # entered, it will be relative to the location where doxygen was started. If 59 # left blank the current directory will be used. 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 65 # will distribute the generated files over these directories. Enabling this 74 # documentation generated by doxygen is written. Doxygen will use this 88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 95 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief [all …]
|
/openbsd-src/usr.sbin/unbound/doc/ |
H A D | unbound.doxygen | 9 # All text after a single hash (#) is considered a comment and will be ignored. 61 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy 67 # into which the generated documentation will be written. If a relative path is 68 # entered, it will be relative to the location where doxygen was started. If 69 # left blank the current directory will be used. 73 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096 75 # and will distribute the generated files over these directories. Enabling this 84 # Controls the number of sub-directories that will be created when 95 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII 97 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode [all …]
|
/openbsd-src/share/man/man5/ |
H A D | port-modules.5 | 78 the ports framework will look for a file named 91 to a module will work as expected. 94 a module will be global to the ports framework, and thus may interfere 116 That is, a port that defines specific dependencies will usually 131 variables will usually drop the version suffix and be simply called 141 Normal client ports will use 157 If several modules define the same hook, hook behaviors will be 165 It will be run right after 172 It will be run right after 179 It will be run right after [all …]
|
/openbsd-src/usr.bin/ssh/ |
H A D | ssh_config.5 | 60 will be used. 256 will require confirmation using the 277 after which it will automatically be removed. 299 will be disabled. 324 will attempt to look up the unqualified hostname using the system resolver's 328 will cause 348 will attempt to canonicalize the hostname specified on the command line 390 will allow hostnames matching 416 character, then the specified algorithms will be appended to the default set 420 character, then the specified algorithms (including wildcards) will b [all...] |
/openbsd-src/gnu/usr.bin/perl/cpan/IO-Compress/lib/IO/Uncompress/ |
H A D | Bunzip2.pm | 229 assumed to be a filename. This file will be opened for reading and the 230 input data will be read from it. 235 data will be read from it. The string '-' can be used as an alias for 241 will be read from C<$$input_filename_or_reference>. 248 The input data will be read from each file in turn. 250 The complete array will be walked to ensure that it only 256 characters "<" and ">" C<bunzip2> will assume that it is an 265 C<undef> will be returned. 278 assumed to be a filename. This file will be opened for writing and the 279 uncompressed data will b [all...] |
H A D | AnyInflate.pm | 195 The module will auto-detect which, if any, of the supported 230 assumed to be a filename. This file will be opened for reading and the 231 input data will be read from it. 236 data will be read from it. The string '-' can be used as an alias for 242 will be read from C<$$input_filename_or_reference>. 249 The input data will be read from each file in turn. 251 The complete array will be walked to ensure that it only 257 characters "<" and ">" C<anyinflate> will assume that it is an 266 C<undef> will be returned. 279 assumed to be a filename. This file will b [all...] |
H A D | Inflate.pm | 288 assumed to be a filename. This file will be opened for reading and the 289 input data will be read from it. 294 data will be read from it. The string '-' can be used as an alias for 300 will be read from C<$$input_filename_or_reference>. 307 The input data will be read from each file in turn. 309 The complete array will be walked to ensure that it only 315 characters "<" and ">" C<inflate> will assume that it is an 324 C<undef> will be returned. 337 assumed to be a filename. This file will be opened for writing and the 338 uncompressed data will b [all...] |
H A D | Gunzip.pm | 366 assumed to be a filename. This file will be opened for reading and the 367 input data will be read from it. 372 data will be read from it. The string '-' can be used as an alias for 378 will be read from C<$$input_filename_or_reference>. 385 The input data will be read from each file in turn. 387 The complete array will be walked to ensure that it only 393 characters "<" and ">" C<gunzip> will assume that it is an 402 C<undef> will be returned. 415 assumed to be a filename. This file will be opened for writing and the 416 uncompressed data will b [all...] |
/openbsd-src/distrib/notes/ |
H A D | m4.common | 186 as a bootable CD-ROM image, but will require the base 209 {:- bsd A stock GENERIC MACHINE kernel which will be 251 OpenBSD kernel will try to discover these parameters on its own, and if it 252 can it will print them at boot time. If possible, you should use the 263 The following is a walk-through of the steps you will take while getting 273 If any question has a default answer, it will be displayed in brackets ("[]") 278 will return you back to that prompt. 286 {:- Once the kernel has loaded, you will be presented with the 291 After the kernel is done initializing, you will be asked whether 300 {:- You will next be asked for your terminal type.-:}, [all …]
|
/openbsd-src/share/man/man8/man8.hppa/ |
H A D | boot_hppa.8 | 41 will proceed to its initialization, and will boot an operating system 62 If autoboot is enabled, the PDC will attempt to boot from the specified 67 has been specified, the PDC will then scan for bootable devices and 70 If autoboot is disabled, the PDC will enter interactive mode, after an 87 command (see below) will be followed by the question: 89 where a positive answer will invoke an interactive prompt in the 91 program later and negative will thus suppress it. 92 A cancellation will abort the boot process. 150 the PDC will always attempt to boot the first bootable device found in 176 setting defines a bootable device, no device scan will occur. [all …]
|
/openbsd-src/lib/libcrypto/man/ |
H A D | EVP_EncodeInit.3 | 129 data will be produced, plus some occasional newlines. 131 will be padded at the end using the "=" character. 145 The final block, which may be less than 48 bytes, will output 4 bytes 149 Similarly a newline character will also be output. 168 Only full blocks of data (48 bytes) will be immediately processed and 172 object and will be processed by a subsequent call to 182 This gives the number of blocks of data that will be processed. 189 will set 192 On success 1 will be returned. 196 It will process any partial block of data remaining in the [all …]
|
/openbsd-src/usr.sbin/pppd/chat/ |
H A D | chat.8 | 69 will prevent both log messages from 78 and all error messages will be sent to 81 Pass in an arbitrary string, usually a phone number, that will be 87 An alternate reply may be sent or the script will fail if there 89 A failed script will cause the 93 Pass in a second string, usually a phone number, that will be 102 program will then log all text received from the modem and the output strings 115 program will then log the execution state of the chat script as well as all 159 program will send the string ppp and then expect the prompt 161 When it receives the prompt for the password, it will send the password [all …]
|
/openbsd-src/share/man/man9/ |
H A D | vfs_cache.9 | 72 points to a pointer where the vnode of the name being sought will be 83 If no entry is found for the given name, a new one will be created, 84 even if the path name fails (i.e. it will be negative cached), unless 97 If locking the vnode fails, the vnode will remain unlocked, 99 will be set to 101 and the corresponding error will be returned. 137 points to where a pointer to the encompassing directory will be stored. 142 the name will be written to the end of the space between this pointer 147 will be updated on return to point to the start of the copied name. 151 will be set to point to the encompassing directory and zero will be [all …]
|
/openbsd-src/share/man/man1/ |
H A D | update-plist.1 | 67 is run as root, but will switch back to 86 But this will speed up packing-list regeneration for ports with 121 Only existing substitutions will be considered for the new lists. 176 and it will scan all paths under that directory and dispatch 180 files that were in existing packing-list(s) will be kept in the same 183 new files and directories will be put in the packing-list that owns 186 barring that, new files will be put into the first packing-list whose PREFIX 190 As far as possible, everything that looks like actual files will be sorted 194 will warn for a lot of conditions, such as pre-formatted manpages, or files 198 will silence the warning. [all …]
|
/openbsd-src/gnu/usr.bin/perl/cpan/IO-Compress/lib/IO/Compress/ |
H A D | Deflate.pm | 194 assumed to be a filename. This file will be opened for reading and the 195 input data will be read from it. 200 data will be read from it. The string '-' can be used as an alias for 206 will be read from C<$$input_filename_or_reference>. 213 The input data will be read from each file in turn. 215 The complete array will be walked to ensure that it only 221 characters "<" and ">" C<deflate> will assume that it is an 230 C<undef> will be returned. 243 assumed to be a filename. This file will be opened for writing and the 244 compressed data will b [all...] |
H A D | Bzip2.pm | 227 assumed to be a filename. This file will be opened for reading and the 228 input data will be read from it. 233 data will be read from it. The string '-' can be used as an alias for 239 will be read from C<$$input_filename_or_reference>. 246 The input data will be read from each file in turn. 248 The complete array will be walked to ensure that it only 254 characters "<" and ">" C<bzip2> will assume that it is an 263 C<undef> will be returned. 276 assumed to be a filename. This file will be opened for writing and the 277 compressed data will b [all...] |
/openbsd-src/gnu/usr.bin/perl/pod/ |
H A D | perlfork.pod | 32 What this means in general is that running fork() will actually clone the 35 point where the fork() was called in the parent. We will refer to the 69 it. All file and directory accesses from the pseudo-process will correctly 75 These calls will properly wait for the termination of the pseudo-process 92 signal will not be delivered while the pseudo-process is blocked by a 95 parent process will not wait for children to exit once they have been 97 exit. You will have to explicitly call waitpid() to make sure the 106 process ID reported within the running executable will be different from 108 manipulation functions applied to the ID returned by fork() will affect the 113 END blocks will still be called after the external process returns. [all …]
|
/openbsd-src/usr.sbin/relayd/ |
H A D | relayd.conf.5 | 39 defining tables in the config file, but those tables will use the 70 will look up the first IPv4 address and any other IPv4 and IPv6 99 Macros can be defined that will later be expanded in context. 132 is omitted, it will default to 137 Set the interval in seconds at which the hosts will be checked. 169 runs 3 relay processes by default and every process will handle 189 or relays; they will be mapped to a 195 Start the table disabled \(en no hosts will be checked in this table. 210 The check will be skipped for this host and copied from the parent host. 220 If not specified, the kernel will se [all...] |