| /freebsd-14.2/contrib/ntp/ |
| H A D | README.pullrequests | 15 on the stable branch, and pull your work into a master copy to allow for 16 publishing your changes in the ntp-dev or master branch. 18 If there is no expectation that your work will be included in the 29 incorporate your work. 38 i) Log on to github.com with your github account. 45 ntp master to your own account. Once done, it will go to your account's 47 iv) Clone a local version of your fork. 54 i) Create a branch off your own master branch of your local fork. 61 keep track of your changes by committing to your local repo. 71 create a pull request on your branch on github. (Read up on [all …]
|
| H A D | README.patches | 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) 15 > (resolve any problems and test your changes) 16 > (commit your changes to ntp-dev) 22 If you make your changes in the above order and then submit them, 23 it will be trivial to apply your patches. 25 Otherwise, it will be much more difficult to apply your patches. 27 You are pretty much done now if your repos are on pogo.udel.edu. 37 If you cannot easily get your patches to pogo, you may submit patches [all …]
|
| /freebsd-14.2/tools/tools/git/ |
| H A D | HOWTO | 13 should demonstrate a logical progression towards your end goal. For example, 18 It usually will not be helpful to present your code in the order in which it 20 introduced a bug early in your development process that you fixed in a 24 presented to your reviewers in any review. 28 gives your reviewers the necessary context to understand your change. 30 2. Create your reviews by running this command in your git repo: 50 to your repository with this command: 59 When you run arc, it will pull up your editor and give you a chance to 79 First, merge each of your review branches back into your main development 97 The rebase will not introduce any actual changes to your code if done [all …]
|
| /freebsd-14.2/sys/contrib/zstd/ |
| H A D | CONTRIBUTING.md | 14 We actively welcome your pull requests. 20 5. Make sure your code lints. 227 * How you aggregate your samples are important. You might be tempted to use the mean of your 235 your improved stability by looking at the size of your confidence intervals as you 252 on your OS: 293 on your computer, benchzstd alone will likely not be enough to validate the impact of your 328 3. Close all other applications except for your instruments window and your terminal 329 4. Run your benchmarking script from your terminal window 337 5. Once you run your benchmarking script, switch back over to instruments and attach your 345 recording), stop your profiler. [all …]
|
| /freebsd-14.2/usr.sbin/bsdconfig/include/ |
| H A D | network_device.hlp | 21 If you're using a modem then PPP is almost certainly your only choice. 22 Make sure that you have your service provider's information handy as 24 will need to know your service provider's IP address, the IP address 25 of your provider's DNS server, and possibly your own IP address unless 26 your ISP supports dynamic negotiation, most do. If you do not choose 28 "AT commands" to dial the ISP with your particular brand of modem as 48 You will also need to know your IP address on the network, the 49 "netmask" value for your address class, and the name of your machine. 50 Your system administrator can tell you which values to use for your 53 possibly the address of a gateway (if you're using PPP, it's your [all …]
|
| /freebsd-14.2/contrib/kyua/ |
| H A D | CONTRIBUTING.md | 6 to get your changes incorporated. 12 * Before we can use your code, you must sign the 16 mainly because you own the copyright to your changes, even after your 17 contribution becomes part of our codebase, so we need your permission to use 18 and distribute your code. We also need to be sure of various other 19 things--for instance that you will tell us if you know that your code 22 but you must do it before we can put your code into our codebase. 28 Please get your company to sign this agreement instead if your contribution is 31 * Unless you have a strong reason not to, please assign copyright of your 68 enable Travis CI builds on your end. Wait for a green result. [all …]
|
| /freebsd-14.2/lib/libc/net/ |
| H A D | networks | 5 your-net 127 # your comment 6 your-netmask 255.255.255 # subnet mask for your-net
|
| H A D | hosts | 5 # share this file. Replace 'my.domain' below with the domainname of your 27 # real official assigned numbers. Do not try to invent your own network 28 # numbers but instead get one from your network provider (if any) or 29 # from your regional registry (ARIN, APNIC, LACNIC, RIPE NCC, or AfriNIC.)
|
| /freebsd-14.2/contrib/googletest/ |
| H A D | CONTRIBUTING.md | 1 # How to become a contributor and submit your own code 5 We'd love to accept your patches! Before we can take them, we have to jump a 14 * If you work for a company that wants to allow you to contribute your work, 20 accept your pull requests. 30 1. Submit an issue describing your proposed change to the 36 This ensures that work isn't being duplicated and communicating your plan 41 5. Fork the desired repo, develop and test your code changes. 42 6. Ensure that your code adheres to the existing style in the sample to which 84 check your formatting. 101 To make sure your changes work as intended and don't break existing [all …]
|
| H A D | README.md | 61 Googletest automatically discovers and runs your tests, eliminating the need 62 to manually register your tests 65 exceptions, and more, making it easy to test your code 67 You can define your own assertions with Googletest, making it simple to 68 write tests that are specific to your code 70 Googletest supports death tests, which verify that your code exits in a 117 runs your test binary, allows you to track its progress via a progress bar, and 124 result output. If your test runner understands TAP, you may find it useful. 127 runs tests from your binary in parallel to provide significant speed-up. 131 your tests. [all …]
|
| /freebsd-14.2/contrib/mandoc/ |
| H A D | INSTALL | 26 Before manually installing mandoc on your system, please check 32 Regarding how packages and ports are maintained for your operating 33 system, please consult your operating system documentation. 43 functionality as your system's "catman", if your operating 48 for your operating system. 51 This script attempts autoconfiguration of mandoc for your system. 127 on your platform, consider the following: 150 please report whatever is missing on your platform. 153 configuration on your platform: 160 to test the libraries installed on your system and the standard [all …]
|
| /freebsd-14.2/share/examples/ipfilter/rules/ |
| H A D | nat-setup | 1 Configuring NAT on your network. 4 To start setting up NAT, we need to define which is your "internal" interface 5 and which is your "external" interface. The "internal" interface is the 10 For example, your internal interface might have an IP# of 10.1.1.1 and be 11 connected to your ethernet, whilst your external interface might be a PPP 14 Thus your network might look like this:
|
| /freebsd-14.2/contrib/traceroute/ |
| H A D | INSTALL | 9 your system attributes and generate an appropriate Makefile from 18 will abort if your compiler is not ANSI compliant. If this happens, use 39 If yor have a really old system, it may be necessary to modify your 40 kernel before traceroute will work. If you want to hack on your kernel, 43 or may not resemble the code in your kernel. It may offer you a place 44 to start but we make no promises. If you do hack your kernel, remember 47 and you're on your own. 50 your system has this bug, you might want to fix it while you're in the 52 including 4.3tahoe. If your version of netinet/ip_icmp.c is any earlier 68 checked this under 4.3 & SunOS 3 but you should double-check your [all …]
|
| /freebsd-14.2/contrib/less/ |
| H A D | README | 17 Software Foundation; either version 3, or (at your option) any 83 your system that configure might not have detected, you may fix the 90 If you choose not to include some features in your version, you may 98 "lesskey" and "lessecho" in your current directory. Test the 125 Depending on your compiler, you may need to convert the source 133 are correct. CC should be the name of your C compiler and 136 either modify the definitions directly in MAKEFILE, or set your 145 5. Run your "make" program and watch the fun. 146 If your "make" requires a flag to import environment variables, 155 LESSKEY.EXE in a directory which is included in your PATH. [all …]
|
| /freebsd-14.2/contrib/sendmail/libmilter/ |
| H A D | README | 52 It is recommended that you build your filters in a location outside of 62 the Makefile in your appropriate obj.*/libmilter build subdirectory if you 66 process limits in your filter. For example, you might look at using 83 specifies three filters. Filters can be specified in your .mc file using 128 INPUT_MAIL_FILTER commands in your .mc file. Alternatively, you can 129 reset its value by setting confINPUT_MAIL_FILTERS in your .mc file. 139 the appropriate locations) to your .mc file: 148 Once you have compiled a filter, modified your .mc file and restarted 160 an error with your command or a problem creating the specified socket. 197 If the sample filter did not log your test email, there are a number of [all …]
|
| /freebsd-14.2/crypto/openssl/external/perl/Text-Template-1.56/ |
| H A D | README | 14 It has come to our attention that you are delinquent in your 16 ${sprintf("%.2f", $amount)} immediately, or your patellae may 29 It has come to our attention that you are delinquent in your 31 $392.12 immediately, or your patellae may 39 You can store a template in a file outside your program. People can 47 won't have to worry that they are tampering with your program when you
|
| /freebsd-14.2/crypto/openssl/doc/HOWTO/ |
| H A D | certificates.txt | 6 How you handle certificates depends a great deal on what your role is. 50 yourself if you have your own certificate authority or create a 67 complete, they send you your new certificate. 88 was kind enough, your certificate is a raw DER thing in PEM format. 91 things like PKCS7 or PKCS12, or something else. Depending on your 96 So, depending on your application, you may have to convert your 97 certificate and your key to various formats, most often also putting 101 right for your applications, simply concatenating the certificate and 106 By now, you have your certificate and your private key and can start
|
| /freebsd-14.2/contrib/dialog/samples/install/ |
| H A D | setup.help | 4 sure that nothing bad is done to your harddisk :-) 26 Setup will ask you for a partition on your harddisk, 29 your local harddisk or via network (NFS). 32 Rebooting your computer with this little linux system 39 create an extra partition on your harddisk for
|
| /freebsd-14.2/contrib/ntp/sntp/libopts/ |
| H A D | README | 12 1. Install the unrolled tarball into your package source tree, 13 copying ``libopts.m4'' to your autoconf macro directory. 15 In your bootstrap (pre-configure) script, you can do this: 32 to your configure.ac file. See LIBOPTS_CHECK: below for details. 34 3. Add the following to your top level ``Makefile.am'' file: 50 you need them in your build tree. 52 5. Make sure your object files explicitly depend upon the 71 If your package does not utilize the auto* tools, then you 120 Public License (see: COPYING.lgpl), or, at your option, the modified
|
| /freebsd-14.2/contrib/googletest/docs/ |
| H A D | quickstart-cmake.md | 5 this tutorial as a starting point. If your project uses Bazel, see the 35 project. You'll use this file to set up your project and declare a dependency on 38 First, create a directory for your project: 48 To do this, in your project directory (`my_project`), create a file named 80 your own project. 82 As an example, create a file named `hello_test.cc` in your `my_project` 98 behavior of your code. The above sample includes the main GoogleTest header file 101 To build the code, add the following to the end of your `CMakeLists.txt` file: 125 Now you can build and run your test:
|
| H A D | quickstart-bazel.md | 29 is a directory on your filesystem that you use to manage source files for the 34 First, create a directory for your workspace: 45 To do this, in the root directory of your workspace (`my_workspace/`), create a 68 With your Bazel workspace set up, you can now use GoogleTest code within your 71 As an example, create a file named `hello_test.cc` in your `my_workspace` 87 behavior of your code. The above sample includes the main GoogleTest header file 115 Now you can build and run your test:
|
| /freebsd-14.2/usr.bin/fortune/datfiles/ |
| H A D | freebsd-tips | 75 someone logs in or out of your system. 84 kilobytes instead of 512-byte blocks, set BLOCKSIZE in your 153 Need to quickly return to your home directory? Type "cd". 170 flag is your gateway. 206 press the scroll lock key again to get your prompt back. 258 To see all of the directories on your FreeBSD system, type 292 To see the MAC addresses of the NICs on your system, type 386 You can make a log of your terminal session with script(1). 522 To easily configure your installed FreeBSD use bsdconfig(8). 528 Run "etcupdate extract" once when your sources match your running system, then run [all …]
|
| /freebsd-14.2/sys/contrib/openzfs/contrib/dracut/ |
| H A D | README.md | 3 2. Set `mountpoint=/` for your root dataset (for compatibility, `legacy` also works, but is not rec… 11 4. Or (b) append `root=zfs:pool/dataset` to your kernel cmdline. 12 5. Re-generate your initrd and update it in your boot bundle 45 …This has obvious potential for data loss: make sure your persistent data is not below the rootfs a…
|
| /freebsd-14.2/etc/sendmail/ |
| H A D | freebsd.mc | 38 # If you want to customize it, copy it to a name appropriate for your 70 dnl Uncomment to allow relaying based on your MX records. 71 dnl NOTE: This can allow sites to use your server as a backup MX without 72 dnl your permission. 82 dnl Uncomment to activate your chosen DNS based block list 84 dnl Alternatively, you can provide your own server and rejection message: 88 dnl define(`SMART_HOST', `your.isp.mail.server')
|
| /freebsd-14.2/crypto/openssh/ |
| H A D | README.dns | 17 where "hostname" is your fully qualified hostname and "keyfile" is the 23 implementations. If your nameserver has support for the SSHFP RR 27 to your DNS zone file and sign your zone.
|