diff options
| author | Scott Rifenbark <srifenbark@gmail.com> | 2017-06-29 13:31:00 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-07-12 00:28:14 +0100 |
| commit | 39e61c9ad9622d805a64413201b308e6a09943d1 (patch) | |
| tree | deb49520125a47288922f7ba92078551cdfe754b /documentation/kernel-dev/kernel-dev-concepts-appx.xml | |
| parent | 64f0f60b3fba36ff87fe78ec1e27e6398d206c51 (diff) | |
| download | poky-39e61c9ad9622d805a64413201b308e6a09943d1.tar.gz | |
kernel-dev: Inserted section on Git as a relavent note
Appendix A of the kernel-dev had a subsection dedicated to just
saying Git was the SCM used by the YP team for development. Having
this information in a dedicated section was overkill. The information
is better as an "aside". I put the stuff in a note.
(From yocto-docs rev: 7e28686f946188daaf0480d4cd68e0e8ff854d37)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev/kernel-dev-concepts-appx.xml')
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-concepts-appx.xml | 59 |
1 files changed, 31 insertions, 28 deletions
diff --git a/documentation/kernel-dev/kernel-dev-concepts-appx.xml b/documentation/kernel-dev/kernel-dev-concepts-appx.xml index ee40938b5d..21f7c2c686 100644 --- a/documentation/kernel-dev/kernel-dev-concepts-appx.xml +++ b/documentation/kernel-dev/kernel-dev-concepts-appx.xml | |||
| @@ -200,10 +200,37 @@ | |||
| 200 | on top of the baseline. | 200 | on top of the baseline. |
| 201 | The features are tagged and organized by way of a branching | 201 | The features are tagged and organized by way of a branching |
| 202 | strategy implemented by the Yocto Project team using the | 202 | strategy implemented by the Yocto Project team using the |
| 203 | source code manager (SCM) Git. | 203 | Source Code Manager (SCM) Git. |
| 204 | For information on Git as applied to the Yocto Project, see the | 204 | <note><title>Notes</title> |
| 205 | "<ulink url='&YOCTO_DOCS_REF_URL;#git'>Git</ulink>" section | 205 | <itemizedlist> |
| 206 | in the Yocto Project Development Manual. | 206 | <listitem><para> |
| 207 | Git is the obvious SCM for meeting the Yocto Linux | ||
| 208 | kernel organizational and structural goals | ||
| 209 | described in this section. | ||
| 210 | Not only is Git the SCM for Linux kernel | ||
| 211 | development in <filename>kernel.org</filename> but, | ||
| 212 | Git continues to grow in popularity and supports | ||
| 213 | many different work flows, front-ends and | ||
| 214 | management techniques. | ||
| 215 | </para></listitem> | ||
| 216 | <listitem><para> | ||
| 217 | You can find documentation on Git at | ||
| 218 | <ulink url='http://git-scm.com/documentation'></ulink>. | ||
| 219 | You can also get an introduction to Git as it | ||
| 220 | applies to the Yocto Project in the | ||
| 221 | "<ulink url='&YOCTO_DOCS_REF_URL;#git'>Git</ulink>" | ||
| 222 | section in the Yocto Project Reference Manual. | ||
| 223 | The latter reference provides an overview of | ||
| 224 | Git and presents a minimal set of Git commands | ||
| 225 | that allows you to be functional using Git. | ||
| 226 | You can use as much, or as little, of what Git | ||
| 227 | has to offer to accomplish what you need for your | ||
| 228 | project. | ||
| 229 | You do not have to be a "Git Expert" in order to | ||
| 230 | use it with the Yocto Project. | ||
| 231 | </para></listitem> | ||
| 232 | </itemizedlist> | ||
| 233 | </note> | ||
| 207 | </para> | 234 | </para> |
| 208 | 235 | ||
| 209 | <para> | 236 | <para> |
| @@ -342,30 +369,6 @@ | |||
| 342 | because the kernel tree is left in this state after cloning and building the kernel. | 369 | because the kernel tree is left in this state after cloning and building the kernel. |
| 343 | </para> | 370 | </para> |
| 344 | </section> | 371 | </section> |
| 345 | |||
| 346 | <section id='source-code-manager-git'> | ||
| 347 | <title>Source Code Manager - Git</title> | ||
| 348 | <para> | ||
| 349 | The Source Code Manager (SCM) is Git. | ||
| 350 | This SCM is the obvious mechanism for meeting the previously mentioned goals. | ||
| 351 | Not only is it the SCM for <filename>kernel.org</filename> but, | ||
| 352 | Git continues to grow in popularity and supports many different work flows, | ||
| 353 | front-ends and management techniques. | ||
| 354 | </para> | ||
| 355 | <para> | ||
| 356 | You can find documentation on Git at <ulink url='http://git-scm.com/documentation'></ulink>. | ||
| 357 | You can also get an introduction to Git as it applies to the Yocto Project in the | ||
| 358 | "<ulink url='&YOCTO_DOCS_REF_URL;#git'>Git</ulink>" | ||
| 359 | section in the Yocto Project Reference Manual. | ||
| 360 | These referenced sections overview Git and describe a minimal set of | ||
| 361 | commands that allows you to be functional using Git. | ||
| 362 | <note> | ||
| 363 | You can use as much, or as little, of what Git has to offer to accomplish what | ||
| 364 | you need for your project. | ||
| 365 | You do not have to be a "Git Master" in order to use it with the Yocto Project. | ||
| 366 | </note> | ||
| 367 | </para> | ||
| 368 | </section> | ||
| 369 | </section> | 372 | </section> |
| 370 | </appendix> | 373 | </appendix> |
| 371 | <!-- | 374 | <!-- |
