| /freebsd-12-stable/contrib/ntp/ |
| D | README.pullrequests | 14 in seeing that work in the current production release then base your work
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
19 current stable release (the ntp-stable code) then it's better to do your
24 It's possible that after pulling your changes from stable to master that
29 incorporate your work.
31 Please also note that your submissions will be able to be evaluated and
32 handled sooner if the repo that contains your pull requests also includes
37 1) If you haven't, create a fork of ntp-project/ntp with your github account.
[all …]
|
| 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-12-stable/tools/tools/git/ |
| D | HOWTO | 14 should demonstrate a logical progression towards your end goal. For example,
16 any current functionality. A subsequent commit could then introduce your new
19 It usually will not be helpful to present your code in the order in which it
21 introduced a bug early in your development process that you fixed in a
22 subsequent commit, it is a waste of your reviewer's time to have them review
25 presented to your reviewers in any review.
29 gives your reviewers the necessary context to understand your change.
31 2. Create your reviews bu running this command in your git repo:
50 Next, make your change and perform whatever testing is necessary. Commit it
51 to your repository with this command:
[all …]
|
| /freebsd-12-stable/contrib/googletest/googletest/docs/ |
| D | XcodeGuide.md | 3 This guide will explain how to use the Google Testing Framework in your Xcode projects on Mac OS X.…
7 Here is the quick guide for using Google Test in your Xcode project.
11 1. Create a new "Shell Tool" target in your Xcode project called something like "UnitTests".
12 …1. Add the gtest.framework to your project and add it to the "Link Binary with Libraries" build ph…
13 1. Add your unit test source code to the "Compile Sources" build phase of "UnitTests".
27 …your own code base, you can add Google Test as an external dependency to your own Subversion repos…
29 …xternals _directory_` to set the svn:externals property on a directory in your repository. This di…
31 The command `svn propedit` will bring up your Subversion editor, making editing the long, (potentia…
42 The next step is to build and add the gtest.framework to your own project. This guide describes two…
44 …your own project, is to open gtest.xcodeproj (found in the xcode/ directory of the Google Test tru…
[all …]
|
| /freebsd-12-stable/usr.sbin/bsdconfig/include/ |
| 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
31 can simply enter `dial' (without the quotes) at the ppp prompt if your
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
[all …]
|
| /freebsd-12-stable/sys/contrib/zstd/ |
| D | CONTRIBUTING.md | 14 We actively welcome your pull requests.
16 1. Fork the repo and create your branch from `dev`.
20 5. Make sure your code lints.
24 In order to accept your pull request, we need you to submit a CLA. You only need
27 Complete your CLA here: <https://code.facebook.com/cla>
30 We use GitHub issues to track public bugs. Please ensure your description is
41 By contributing to Zstandard, you agree that your contributions will be licensed
|
| /freebsd-12-stable/lib/libc/net/ |
| D | networks | 6 your-net 127 # your comment
7 your-netmask 255.255.255 # subnet mask for your-net
|
| D | hosts | 6 # share this file. Replace 'my.domain' below with the domainname of your
28 # real official assigned numbers. Do not try to invent your own network
29 # numbers but instead get one from your network provider (if any) or
30 # from your regional registry (ARIN, APNIC, LACNIC, RIPE NCC, or AfriNIC.)
|
| /freebsd-12-stable/contrib/gcc/ |
| D | config.in | 163 /* Define if your assembler supports dwarf2 .file/.loc directives, and
170 /* Define if your assembler supports explicit relocations. */
176 /* Define if your assembler supports fprnd. */
182 /* Define if your assembler supports the --gdwarf2 option. */
194 /* Define if your assembler supports the --gstabs option. */
200 /* Define if your assembler supports the Sun syntax for cmov. */
206 /* Define if your assembler supports the ffreep mnemonic. */
212 /* Define if your assembler supports the lituse_jsrdirect relocation. */
218 /* Define if your assembler supports .sleb128 and .uleb128. */
224 /* Define if your assembler supports ltoffx and ldxmov relocations. */
[all …]
|
| /freebsd-12-stable/contrib/googletest/ |
| 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
14 * If you work for a company that wants to allow you to contribute your work,
20 accept your pull requests.
28 1. Submit an issue describing your proposed change to the
36 communicating your plan early also generally leads to better
38 1. If your proposed change is accepted, and you haven't already done so, sign a
40 1. Fork the desired repo, develop and test your code changes.
41 1. Ensure that your code adheres to the existing style in the sample to which
43 1. Ensure that your code has an appropriate set of unit tests which all pass.
[all …]
|
| /freebsd-12-stable/share/examples/diskless/ |
| D | ME | 29 For example, your /etc/rc.conf.local should become a softlink to
30 /conf/ME/rc.conf.local and your real rc.conf.local should go into the
34 to start an X session up on boot on certain of your machines ).
36 When templating, you duplicate your / and /usr partitions on each machine's
41 There are often categories of configuration files. For example, all of your
42 shell machines may use one resolv.conf while all of your mail proxies may
48 softlink. The advantage is that for all the complexity of your /conf
49 directory hierarchy, most of your common config files exist in only one place
|
| /freebsd-12-stable/contrib/mandoc/ |
| 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.
107 If your system does not have them, the bundled compatibility version
115 If your system does not have it, the bundled compatibility version
127 on your platform, consider the following:
133 longer. If your system does need such magic, consider upgrading
[all …]
|
| /freebsd-12-stable/contrib/traceroute/ |
| 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-12-stable/contrib/less/ |
| D | README | 19 Software Foundation; either version 3, or (at your option) any
80 your system that configure might not have detected, you may fix the
87 If you choose not to include some features in your version, you may
95 "lesskey" and "lessecho" in your current directory. Test the
122 Depending on your compiler, you may need to convert the source
130 are correct. CC should be the name of your C compiler and
133 either modify the definitions directly in MAKEFILE, or set your
138 If you choose not to include some features in your version, you may
142 5. Run your "make" program and watch the fun.
143 If your "make" requires a flag to import environment variables,
[all …]
|
| /freebsd-12-stable/contrib/sendmail/libmilter/ |
| D | README | 49 It is recommended that you build your filters in a location outside of
53 -lsocket -lnsl'. Depending on your operating system you may need a library
59 the Makefile in your appropriate obj.*/libmilter build subdirectory if you
63 process limits in your filter. For example, you might look at using
64 setrlimit() to increase the number of open file descriptors if your filter
80 specifies three filters. Filters can be specified in your .mc file using
125 INPUT_MAIL_FILTER commands in your .mc file. Alternatively, you can
126 reset its value by setting confINPUT_MAIL_FILTERS in your .mc file.
132 filter list by using MAIL_FILTER() instead of INPUT_MAIL_FILTER() in your
136 the appropriate locations) to your .mc file:
[all …]
|
| /freebsd-12-stable/share/examples/ipfilter/rules/ |
| 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-12-stable/crypto/openssl/doc/HOWTO/ |
| 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-12-stable/contrib/opie/ |
| D | BUG-REPORT | 5 sure that your "bug" is not a known problem.
7 Please make a copy of this file and then edit it with your favorite
16 please provide the output of "uname -a" and/or the version of your C
31 If your system has the script(1) command, please run a session
53 your mailer.
55 * DO NOT send a copy of your bug report to ANYONE other than
59 * DO NOT send a copy of your bug report directly to the
71 to all properly submitted bug reports as soon as we can. If your bug report
73 takes one working day. If our machine sorter can't process your bug report,
|
| /freebsd-12-stable/usr.bin/fortune/datfiles/ |
| D | freebsd-tips | 43 If other operating systems have damaged your Master Boot Record, you can
54 If you have a CD-ROM drive in your machine, you can make the CD-ROM that is
62 If you need a reminder to leave your terminal, type "leave +hhmm" where
78 someone logs in or out of your system.
80 If you use the C shell, add the following line to the .cshrc file in your
87 kilobytes instead of 512-byte blocks, set BLOCKSIZE in your
134 "man security" gives very good advice on how to tune the security of your
137 "man tuning" gives some tips how to tune performance of your FreeBSD system.
148 Need to leave your terminal for a few minutes and don't want to logout?
149 Use "lock -p". When you return, use your password as the key to unlock the
[all …]
|
| /freebsd-12-stable/contrib/ntp/sntp/libopts/ |
| 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-12-stable/contrib/ipfilter/ |
| D | NAT.FreeBSD | 17 6) Configure your network interfaces
25 If you are using a Kernal Loadable Module you need to edit your
36 put in the rules that you need for your system.
68 In your /etc/rc.local put the line:
87 Edit your /etc/sysconfig to add them at bootup.
94 6) Make sure that you have your interfaces configured.
|
| /freebsd-12-stable/usr.sbin/cron/doc/ |
| D | README | 5 # * documentation (don't take credit for my work), mark your changes (don't
6 # * get me blamed for your possible bugs), don't alter or remove this
9 # * software; use at your own risk, responsibility for damages (if any) to
58 kill your existing cron process
59 (actually you can run your existing cron if you want, but why?)
67 watch it. test it with 'crontab -r' and watch the daemon track your
69 if you like it, change your /etc/{rc,rc.local} to use it instead of
|
| /freebsd-12-stable/contrib/googletest/googletest/ |
| D | README.md | 5 To build Google Test and your tests that use it, you need to tell your build
27 Next, you should compile your test source file with `${GTEST_DIR}/include` in
38 point for your own build script.
40 If the default settings are correct for your environment, the following commands
59 the compiler environment of your choice. You can either build Google Test as a
93 between gtest and the rest of your project, so issues associated with using
197 integrate Google Test with your existing build system.
212 Build the "gtest" target. The universal binary framework will end up in your
218 This will build the "Release" configuration of gtest.framework in your default
252 However, if your project already uses TR1 tuple, you need to tell Google Test to
[all …]
|
| /freebsd-12-stable/tools/tools/tinybsd/ |
| D | CHANGES | 4 - Added function personal_directories, you can create on conf dir your custom
5 personal directories with your custom files inside of them and it will be copied
6 to your image.
29 - added etc/ on each image directory to the user copy your custom etc
|
| /freebsd-12-stable/contrib/googletest/googlemock/docs/ |
| D | FrequentlyAskedQuestions.md | 3 Please send your questions to the
19 Unfortunately, this means that if you have defined your own matchers
21 your definitions will no longer compile. Matchers defined using the
24 Sorry for the hassle if your matchers are affected. We believe it's
29 If you wrote your matcher like this:
112 If your matcher is defined using `MakePolymorphicMatcher()`:
151 If your polymorphic matcher uses `ExplainMatchResultTo()` for better
208 to configure it to work with any testing framework of your choice.
216 problems (we call them diseases) your code has.
225 <your-favorite-build-command> <your-test> 2>&1 | gmd
[all …]
|