commit | d58be1cb16e62a9821b6dbd0157b8c7ff0b667ec | [log] [tgz] |
---|---|---|
author | Filippo Valsorda <hi@filippo.io> | Wed Jun 05 11:25:04 2024 +0200 |
committer | Gopher Robot <gobot@golang.org> | Wed Jun 26 14:12:39 2024 +0000 |
tree | a3c3ddbf84b8fe84eba576c3afdaa4cca5335a1f | |
parent | 232e49f555b427208443629fdd6870f71917c249 [diff] |
sumdb/tlog: set the hash of the empty tree according to RFC 6962 Updates FiloSottile/sunlight#14 Change-Id: I712ea53fd3a17b66ec310d8f48de44416d0054cc Reviewed-on: https://go-review.googlesource.com/c/mod/+/590715 Reviewed-by: Russ Cox <rsc@golang.org> Auto-Submit: Filippo Valsorda <filippo@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Joedian Reid <joedian@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.