Lines Matching refs:topic

38 The KVM x86 tree is organized into multiple topic branches.  The purpose of
39 using finer-grained topic branches is to make it easier to keep tabs on an area
41 commits, e.g. dropping the HEAD commit of a topic branch has no impact on other
43 delays only that topic branch.
45 All topic branches, except for ``next`` and ``fixes``, are rolled into ``next``
46 via a Cthulhu merge on an as-needed basis, i.e. when a topic branch is updated.
55 requests (from KVM x86 to main KVM) are sent for each KVM x86 topic branch,
57 following rc7 for "normal" releases.  If all goes well, the topic branches are
94 select a specific topic branch as the base.  If there are conflicts and/or
95 dependencies across topic branches, it is the maintainer's job to sort them
150 The preferred prefix format is ``KVM: <topic>:``, where ``<topic>`` is one of::
166 Note, these don't align with the topics branches (the topic branches care much
185 you want to propose introducing a new topic, i.e. don't go rogue.
338 set to the base topic branch, e.g. it will do the wrong thing if your upstream
341 KVM x86 topic, and feed that into ``--base``.  E.g. ``x86/pmu/my_branch_name``,
364 notification will include the tree and topic branch, along with the SHA1s of