@@ -137,7 +137,7 @@ workspace) is different from remote storage. Bringing the two into sync requires
137
137
138
138
- ` -v ` , ` --verbose ` - displays detailed tracing information.
139
139
140
- ## Example: Simple usage
140
+ ## Examples
141
141
142
142
``` dvc
143
143
$ dvc status
@@ -160,6 +160,24 @@ This shows that for stage `bar.dvc`, the dependency `foo` and the
160
160
<abbr >output</abbr > ` bar ` have changed. Likewise for ` foo.dvc ` , the dependency
161
161
` foo ` has changed, but no output has changed.
162
162
163
+ ## Example: Specific targets
164
+
165
+ ` dvc status ` supports granularity for files found in tracked directories, for
166
+ example:
167
+
168
+ ``` dvc
169
+ $ tree data
170
+ data
171
+ βββ raw
172
+ β βββ partition.1.dat
173
+ β βββ ...
174
+ β βββ partition.n.dat
175
+ βββ raw.dvc # data/raw/ is tracked as a whole.
176
+
177
+ $ dvc status -r local data/raw/partition.1.dat
178
+ new: data/raw
179
+ ```
180
+
163
181
## Example: Dependencies
164
182
165
183
``` dvc
@@ -202,22 +220,6 @@ new: data/matrix-test.p
202
220
The output shows where the location of the remote storage is, as well as any
203
221
differences between the <abbr >cache</abbr > and ` storage ` remote.
204
222
205
- Note that ` dvc status ` supports granularity for files found in tracked
206
- directories, for example:
207
-
208
- ``` dvc
209
- $ tree data
210
- data
211
- βββ raw
212
- β βββ partition.1.dat
213
- β βββ ...
214
- β βββ partition.n.dat
215
- βββ raw.dvc # data/raw/ is tracked as a whole.
216
-
217
- $ dvc status -r local data/raw/partition.1.dat
218
- new: data/raw
219
- ```
220
-
221
223
## Example: Import stage needs update
222
224
223
225
Let's import a data file (` data.csv ` ) from a different <abbr >DVC repository
0 commit comments