Lines Matching refs:status

2908 consider checking on the upgrade status of a recipe first. You can do so
2909 using the ``devtool check-upgrade-status`` command. See the
2910 ":ref:`devtool-checking-on-the-upgrade-status-of-a-recipe`"
3080    well as a status email, use the following command::
9082          command returns a tuple: (status, output), which are what their
9773 the console as "silent" as possible. Also, if you want status messages
10558 merging patches. Thus, you can get an idea of the status of a patch based on
10742 to track the status of patches submitted to the various mailing lists and to
10751    Asking about the status of a patch or change is reasonable if the change
10896 The list of stable branches along with the status and maintainer for each
11480 unpatched CVEs and the status of patches. Such information is available for
11514 -  status of each CVE: ``Patched``, ``Unpatched`` or ``Ignored``
11516 The status ``Patched`` means that a patch file to address the security issue has been
11517 applied. ``Unpatched`` status means that no patches to address the issue have been
11559 It is also possible to check the CVE status of individual packages as follows::
11619 CVE checker will then capture this information and change the CVE status to ``Patched``