| commit | 74241a19c1864706508bfa12510fc7d6e53d91cc | [log] [tgz] |
|---|---|---|
| author | thepudds <pj_malloy@yahoo.com> | Tue Jul 31 13:31:00 2018 -0400 |
| committer | thepudds <pj_malloy@yahoo.com> | Tue Jul 31 13:31:00 2018 -0400 |
| tree | 7709172a4825e0a437c49794a233490428eca94f | |
| parent | 94d48cbf68999301e3a4fa4a401548580a14b853 [diff] |
I had previously added 'go mod -sync' as a step for the 'Preparing a release' section. Given that, updated step #3 in 'Defining a module' section: rather than 'go mod -sync', say 'go build ./...', which seems more to be the norm (e.g., based on spot checking a couple recent rsc examples). Overall, this section could still be improved/clarified.