Hash1: Make comment more precisely describe how to emulate logic from shell#7
Conversation
… shell The shell command previously given as an example emits paths starting with `./`, and without an added prefix. Also, previously, `sha256` was run against the sorted list of filenames, not against the _contents_ of those files (`xargs` is needed to perform the latter). This does introduce a GNUism; working with POSIX `find` might involve adding a `sed` pipeline element.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). For more information, open the CLA check for this pull request. |
|
This PR (HEAD: abcd998) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/mod/+/394894 to see it. Tip: You can toggle comments from me using the |
|
Message from Gopher Robot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be Please don’t reply on this GitHub thread. Visit golang.org/cl/394894. |
|
Message from Bryan Mills: Patch Set 1: (2 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/394894. |
|
Message from Bryan Mills: Patch Set 1: (2 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/394894. |
2 participants
The shell command previously given as an example emits paths starting with
./, and without an added prefix. Also, previously,sha256was run against the sorted list of filenames, not against the contents ofthose files (
xargsis needed to perform the latter).This does introduce a GNUism; working with POSIX
findmight involve adding asedpipeline element.