diff options
| author | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2018-12-04 18:12:09 +0900 |
|---|---|---|
| committer | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2018-12-06 16:35:59 +0900 |
| commit | 3b7f8df8c6b0f69006e16f0970a124b4ff17aae0 (patch) | |
| tree | 6a438c1b5ba7b0015ae37f72e327aa249da8c584 | |
| parent | 03028c7f3d23b51879e362700e74f14a40755c3c (diff) | |
| download | buildstream-3b7f8df8c6b0f69006e16f0970a124b4ff17aae0.tar.gz | |
Source: Fix typo in documentation, and make it a link to `bst track`
Now the commands have documentation linkability so we can link to
them when referring to them anywhere in the docs. This reference
was previously referring to a bogus non-existent `build-stream track`,
maybe this dates way back to the days before we named the frontend `bst`.
| -rw-r--r-- | buildstream/source.py | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/buildstream/source.py b/buildstream/source.py index d6681b963..5dc5abb63 100644 --- a/buildstream/source.py +++ b/buildstream/source.py @@ -391,7 +391,8 @@ class Source(Plugin): If the backend in question supports resolving references from a symbolic tracking branch or tag, then this should be implemented - to perform this task on behalf of ``build-stream track`` commands. + to perform this task on behalf of :ref:`bst track <invoking_track>` + commands. This usually requires fetching new content from a remote origin to see if a new ref has appeared for your branch or tag. If the |