os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix minor markup issues with updating vendor import section

Browse source
This commit is contained in:
Warner Losh 2021-02-04 10:49:28 -07:00
parent b3f6ba6ff5
commit 4830802786
1 changed files with 0 additions and 2 deletions

2
documentation/content/en/books/developers-handbook/policies/chapter.adoc
View file

@ -82,7 +82,6 @@ Because it makes it harder to import future versions minor, trivial and/or cosme
This section describes the vendor import procedure with Git in detail. This section describes the vendor import procedure with Git in detail.
[.conventions]
==== Branch naming convention ==== Branch naming convention
All vendor branches and tags start with `vendor/`. These branches and All vendor branches and tags start with `vendor/`. These branches and
tags are visible by default. tags are visible by default.
@ -96,7 +95,6 @@ This chapter follows the convention that the `freebsd` origin is the source of t
We'll explore an example for updating NetBSD's mtree that's in our We'll explore an example for updating NetBSD's mtree that's in our
tree. The vendor branch for this is `vendor/NetBSD/mtree`. tree. The vendor branch for this is `vendor/NetBSD/mtree`.
[.procedure]
==== Updating an old vendor import ==== Updating an old vendor import
Since the trees we have in vendor branches are usually a tiny subset of Since the trees we have in vendor branches are usually a tiny subset of
the FreeBSD, it's best to do them with work trees since the process is the FreeBSD, it's best to do them with work trees since the process is