5. Record reference to data in git (but not datafile):
5. Record reference to data in git (but not the datafile itself):
```bash
```bash
git add data/datafile.dat.dvc data/.gitignore
git add data/datafile.dat.dvc data/.gitignore
git commit -m"data generation v1"
git commit -m"data generation v1"
...
@@ -108,7 +110,7 @@ git commit -m "new version of generated data"
...
@@ -108,7 +110,7 @@ git commit -m "new version of generated data"
dvc remote add -dlocal ../dvc-testing-remote
dvc remote add -dlocal ../dvc-testing-remote
```
```
Note: `-d` option is to set the new remote as the default one.
**Note**: `-d` option is to set the new remote as the default one.
9. Push to local DVC remote:
9. Push to local DVC remote:
```bash
```bash
...
@@ -130,7 +132,7 @@ outs:
...
@@ -130,7 +132,7 @@ outs:
path: datafile.dat
path: datafile.dat
```
```
Note: we can verify that the hash stored in the `data/datafile.dat.dvc` file corresponds to the actual `data/datafile.dat` file:
**Note**: we can verify that the hash stored in the `data/datafile.dat.dvc` file corresponds to the actual `data/datafile.dat` file.
```bash
```bash
md5sum data/datafile.dat
md5sum data/datafile.dat
```
```
...
@@ -172,7 +174,7 @@ outs:
...
@@ -172,7 +174,7 @@ outs:
path: datafile.dat
path: datafile.dat
```
```
Note: at this point, the datafile version does not correspond (discrepancy between the hash stored in the `data/datafile.dat.dvc` file and the actual `data/datafile.dat` file:
**Note**: at this point, the actual datafile version does not correspond to the version for this specific git commit (discrepancy between the hash stored in the `data/datafile.dat.dvc` file and the actual `data/datafile.dat` file.