diff options
| author | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2018-12-04 18:12:09 +0900 |
|---|---|---|
| committer | Tristan Van Berkom <tristan.van.berkom@gmail.com> | 2019-08-05 03:54:44 +0000 |
| commit | ad18979c28a94d9664b50ccba40d158d52d29dae (patch) | |
| tree | 47e16cd6fffbafc9ff982199e2430138149437a6 | |
| parent | 2eb6559ee73f2e50919803ee151bd891c8d25669 (diff) | |
| download | buildstream-ad18979c28a94d9664b50ccba40d158d52d29dae.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 24e5b6c5b..7a705b487 100644 --- a/buildstream/source.py +++ b/buildstream/source.py @@ -404,7 +404,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 |