17.1. | Why are trivial or cosmetic changes to files on a vendor branch a bad idea? | ||||||||||||||
| |||||||||||||||
17.2. | How do I add a new file to a branch? | ||||||||||||||
To add a file onto a branch, simply checkout or update
to the branch you want to add to and then add the file
using the add operation as you normally would. This works
fine for the | |||||||||||||||
17.3. | What “meta” information should I include in a commit message? | ||||||||||||||
As well as including an informative message with each commit you may need to include some additional information as well. This information consists of one or more lines containing the key word or phrase, a colon, tabs for formatting, and then the additional information. The key words or phrases are:
Example 1. Commit Log for a Commit Based on a PR You want to commit a change based on a PR submitted by John Smith containing a patch. The end of the commit message should look something like this. ...
PR: foo/12345
Submitted by: John Smith <John.Smith@example.com> Example 2. Commit Log for a Commit Needing Review You want to change the virtual memory system. You
have posted patches to the appropriate mailing list (in
this case, ...
Reviewed by: -arch Example 3. Commit Log for a Commit Needing Approval You want to commit a change to a section of the tree with a MAINTAINER assigned. You have collaborated with the listed MAINTAINER, who has told you to go ahead and commit. ...
Approved by: abc Where Example 4. Commit Log for a Commit Bringing in Code from
OpenBSD You want to commit some code based on work done in the OpenBSD project. ...
Obtained from: OpenBSD Example 5. Commit Log for a Change to FreeBSD-CURRENT with a
Planned Commit to FreeBSD-STABLE to Follow at a Later
Date. You want to commit some code which will be merged from FreeBSD-CURRENT into the FreeBSD-STABLE branch after two weeks. ...
MFC after: 2 weeks Where In some cases you may need to combine some of these. Consider the situation where a user has submitted a PR
containing code from the NetBSD project. You are looking
at the PR, but it is not an area of the tree you normally
work in, so you have decided to get the change reviewed by
the The extra information to include in the commit would look something like PR: foo/54321
Submitted by: John Smith <John.Smith@example.com>
Reviewed by: -arch
Obtained from: NetBSD
MFC after: 1 month | |||||||||||||||
17.4. | How do I access
| ||||||||||||||
| |||||||||||||||
17.5. | Where are the mailing list archives stored? | ||||||||||||||
The mailing lists are archived under
| |||||||||||||||
17.6. | I would like to mentor a new committer. What process do I need to follow? | ||||||||||||||
See the New Account Creation Procedure document on the internal pages. |
This, and other documents, can be downloaded from http://ftp.FreeBSD.org/pub/FreeBSD/doc/
For questions about FreeBSD, read the
documentation before
contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.