| /freebsd/tools/tools/git/ |
| H A D | HOWTO | 13 should demonstrate a logical progression towards your end goal. For example,
15 any current functionality. A subsequent commit could then introduce your new
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
21 subsequent commit, it is a waste of your reviewer's time to have them review
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:
49 Next, make your change and perform whatever testing is necessary. Commit it
50 to your repository with this command:
[all …]
|
| /freebsd/sys/contrib/zstd/ |
| H A 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>
37 * Checkout your fork of zstd if you have not already
42 * Update your local dev branch
48 * Make a new branch on your fork about the topic you're developing for
60 * Note: run local tests to ensure that your changes didn't break existing functionality
71 …* Before sharing anything to the community, create a pull request in your own fork against the dev…
[all …]
|
| /freebsd/contrib/ntp/ |
| H A 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 …]
|
| 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/share/doc/usd/07.mail/ |
| H A D | mail3.nr | 36 where you wish to keep your folders. Each folder of messages will
37 be a single file. For convenience, all of your folders are kept in
38 a single directory of your choosing. To tell
40 where your folder directory is, put a line of the form
44 in your
46 file. If, as in the example above, your folder directory does not
49 will assume that your folder directory is to be found starting from
50 your home directory. Thus, if your home directory is
54 to find your folder directory in
71 command are automatically removed from your system mailbox.
[all …]
|
| H A D | mail2.nr | 42 then type your message. When you reach the end of the message, type
50 to alert him to the existence of your message.
64 to save your partial letter on the file
66 in your home directory and abort the letter.
71 The message your recipient reads will consist of the message you
72 typed, preceded by a line telling who sent the message (your login name)
99 your command. The messages are assigned numbers starting with 1 \*- you
104 (have been sent since you last read your mail) and
116 into your messages.
163 Frequently, it is useful to read the messages in your mailbox in order,
[all …]
|
| H A D | mail4.nr | 45 which will print a line of dashes, the recipients of your message, and
51 ~ escape without killing your letter.
60 your satisfaction, write it out and quit the editor.
67 after which you may continue typing text which will be appended to your
84 editor, on your current message, you can use the escape,
96 file in your message; the escape
101 to your current message.
105 characters appended to your message is printed, after which you may continue
107 which are expanded according to the conventions of your shell.
115 in your home directory. This is often useful since
[all …]
|
| H A D | mail5.nr | 32 reading your mail, setting options, and handling lists of messages.
165 tilde escapes. The subject in your reply is formed by prefacing the
175 You type in your message using the same conventions available to you
207 your mail to a single account.
231 command allows you to change your current directory.
236 changes to your home directory.
270 When you have edited the message to your satisfaction, write the message
291 without updating the system mailbox or the file your were reading.
294 to avoid scrambling your mailbox.
301 List the names of the folders in your folder directory.
[all …]
|
| H A D | mail1.nr | 64 and collects them in a file, called your
67 waiting in your system mailbox. If you are a
70 the shell of the location of your mailbox. On version 7 systems,
71 your system mailbox is located in the directory /var/mail
72 in a file with your login name. If your login name is
76 notify you of new mail by including the following line in your .cshrc
81 When you read your mail using
83 it reads your system mailbox and separates that file into the
|
| /freebsd/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
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/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
21 after you have submitted your code for review and a member has approved it,
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
[all …]
|
| /freebsd/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
38 4. If your proposed change is accepted, and you haven't already done so, sign a
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
44 7. Ensure that your code has an appropriate set of unit tests which all pass.
[all …]
|
| H A D | README.md | 57 Googletest automatically discovers and runs your tests, eliminating the need
58 to manually register your tests
61 exceptions, and more, making it easy to test your code
63 You can define your own assertions with Googletest, making it simple to
64 write tests that are specific to your code
66 Googletest supports death tests, which verify that your code exits in a
113 runs your test binary, allows you to track its progress via a progress bar, and
120 result output. If your test runner understands TAP, you may find it useful.
123 runs tests from your binary in parallel to provide significant speed-up.
127 your tests.
[all …]
|
| /freebsd/crypto/openssl/doc/HOWTO/ |
| H A D | certificates.txt | 6 How you handle certificates depends a great deal on what your role is.
7 Your role can be one or several of:
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.
89 Your key most definitely is if you have followed the examples above.
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
[all …]
|
| /freebsd/share/man/man7/ |
| H A D | security.7 | 101 nearly impossible to stop short of cutting your system off from the Internet.
102 It may not be able to take your machine down, but it can fill up your Internet
115 one or more of your users logging into your system from a remote location
149 to your security because it will not close off the hole the attacker used to
186 For example, make sure that your PTYs are specified as being
248 intruder to break root if the intruder has gotten hold of your password
256 An indirect way to secure the root account is to secure your staff accounts
271 the machines which run the Kerberos servers and your desktop workstation.
275 (typically your workstation),
291 if your main box is running all sorts of servers, your workstation should not
[all …]
|
| /freebsd/usr.bin/fortune/datfiles/ |
| H A D | freebsd-tips | 41 If other operating systems have damaged your Master Boot Record, you can
52 If you have a CD-ROM drive in your machine, you can make the CD-ROM that is
60 If you need a reminder to leave your terminal, type "leave +hhmm" where
75 someone logs in or out of your system.
77 If you use the C shell, add the following line to the .cshrc file in your
84 kilobytes instead of 512-byte blocks, set BLOCKSIZE in your
131 "man security" gives very good advice on how to tune the security of your
134 "man tuning" gives some tips how to tune performance of your FreeBSD system.
145 Need to leave your terminal for a few minutes and don't want to logout?
146 Use "lock -p". When you return, use your password as the key to unlock the
[all …]
|
| /freebsd/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.
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/lib/libc/net/ |
| H A D | networks | 1 # Your Local Networks Database
3 your-net 127 # your comment
4 your-netmask 255.255.255 # subnet mask for your-net
7 # Your subnets
|
| /freebsd/contrib/sendmail/libmilter/ |
| H A D | README | 52 It is recommended that you build your filters in a location outside of
56 -lsocket -lnsl'. Depending on your operating system you may need a library
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
67 setrlimit() to increase the number of open file descriptors if your filter
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.
135 filter list by using MAIL_FILTER() instead of INPUT_MAIL_FILTER() in your
139 the appropriate locations) to your .mc file:
[all …]
|
| /freebsd/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
141 If you choose not to include some features in your version, you may
145 5. Run your "make" program and watch the fun.
146 If your "make" requires a flag to import environment variables,
[all …]
|
| /freebsd/sys/contrib/openzfs/.github/ |
| H A D | CONTRIBUTING.md | 46 or install stable packages from [your distribution's
76 found anything similar to your issue.
96 Be prepared to work with the developers investigating your issue. Your
100 * Your pool configuration as reported by `zdb` or `zpool status`.
101 * Your hardware configuration, such as
104 * Whether your system has ECC memory.
118 If you have an idea for a feature first check this list. If your idea already
122 Otherwise, open a new issue and describe your proposed feature. Why is this
133 * Make sure your commit messages are in the correct format. See the
137 * For large pull requests consider structuring your changes as a stack of
[all …]
|
| H A D | PULL_REQUEST_TEMPLATE.md | 1 <!--- Please fill out the following template, which will help other contributors review your Pull R…
3 <!--- Provide a general summary of your changes in the Title above -->
15 <!--- Describe your changes in detail -->
18 <!--- Please describe in detail how you tested your changes. -->
19 <!--- Include details of your testing environment, and the tests you ran to -->
20 <!--- see how your change affects other areas of the code, etc. -->
21 <!--- If your change is a performance enhancement, please provide benchmarks here. -->
25 <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
|
| /freebsd/crypto/openssl/test/ |
| H A D | proxy.cnf | 17 0.commonName = Common Name (eg, YOUR name)
19 1.commonName = Common Name (eg, YOUR name)
21 2.commonName = Common Name (eg, YOUR name)
42 0.commonName = Common Name (eg, YOUR name)
44 1.commonName = Common Name (eg, YOUR name)
46 2.commonName = Common Name (eg, YOUR name)
48 3.commonName = Common Name (eg, YOUR name)
|
| /freebsd/contrib/sendmail/vacation/ |
| H A D | vacation.1 | 50 reading your mail.
56 file. For example, your
62 which would send messages to you (assuming your login name was eric) and
92 This should only be used on the command line, not in your
109 before you modify your
112 This should only be used on the command line, not in your
120 This should only be used on the command line, not in your
136 This should only be used on the command line, not in your
193 This should only be used on the command line, not in your
263 in your home directory.
[all …]
|
| /freebsd/share/doc/usd/11.vitut/ |
| H A D | edittut.ms | 170 You can review your text
176 rearranges your text
191 other features of \s-2UNIX\s0 will be very important to your work.
197 you are familiar with (1) your terminal and its special keys,
207 such as balancing your checkbook
208 or editing your text.
239 The sizes of files vary to suit your needs;
280 or over a telephone line where the computer answers your call.
284 Turn on your terminal and press the \s-1RETURN\s0 key.
289 If your terminal connects with the computer over a telephone line,
[all …]
|