| commit | 6686f416970d4b8e2f54f521955dee89e6763c4b | [log] [tgz] |
|---|---|---|
| author | Michael Matloob <matloob@golang.org> | Tue May 07 16:01:29 2024 -0400 |
| committer | Michael Matloob <matloob@golang.org> | Tue May 07 20:35:40 2024 +0000 |
| tree | 5f8e2a443df90ec9c31a1f6b7997c52edf44d394 | |
| parent | aa51b25a4485b19ca64f578bad6fa40229e75984 [diff] |
module: add COM0 and LPT0 to badWindowsNames They have been added to the list of file names that are disallowed on Windows that's referenced in the comment to badWindowsNames, so add them to badWindowsNames. For golang/go#67238 For golang/go#66625 Change-Id: I82e5d70f33330f746783fd22090a3ebaf9408dfc Reviewed-on: https://go-review.googlesource.com/c/mod/+/583836 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Sam Thanawalla <samthanawalla@google.com>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.