diff options
| author | Blaise Thompson <blaise@untzag.com> | 2018-05-10 12:54:07 -0500 |
|---|---|---|
| committer | Blaise Thompson <blaise@untzag.com> | 2018-05-10 12:54:07 -0500 |
| commit | 10898eded280c3e7f072f5bd0fa881422b5b0733 (patch) | |
| tree | daa5b4f4ee4c62e1629435c5d4ad604eca5816bd /software | |
| parent | 0818b9f1287ec87d46a53d76172c9e03a398c34b (diff) | |
2018-05-10 12:54
Diffstat (limited to 'software')
| -rw-r--r-- | software/chapter.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/software/chapter.tex b/software/chapter.tex index 372acdf..50a9e75 100644 --- a/software/chapter.tex +++ b/software/chapter.tex @@ -238,7 +238,7 @@ change (feature addition, bugfix, etc). % Typically version control is coupled with uploading to a remote server, for example using git with
GitHub \cite{GitHub}, GitLab \cite{GitLab} or git.chem.wisc.edu \cite{git.chem.wisc.edu}, but
version control need not be synonymous with uploading and distribution. %
-Tools like git have a lot of fantastic features beyond simply saving [CITE], but those are beyond the
+Tools like git have a lot of fantastic features beyond simply saving, but those are beyond the
scope of these ``good enough'' recommendations. %
Also consider defining a version for the software package as a whole. %
Use semantic versioning (MAJOR.MINOR.PATCH) \cite{SemanticVersioning}, unless there is a strong
|