Next | Query returned 7 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2021-07-17 09:12:40 by Nia Alarie | Files touched by this commit (5) | Package removed
Log message:
go-mod: remove

deprecated go-package; no users in pkgsrc
   2021-07-13 13:36:45 by Benny Siegert | Files touched by this commit (132) | Package updated
Log message:
Revbump all Go packages after go116 update
   2021-06-06 14:19:04 by Benny Siegert | Files touched by this commit (203) | Package updated
Log message:
Revbump all Go packages after go116 update
   2021-05-08 17:02:47 by Benny Siegert | Files touched by this commit (216) | Package updated
Log message:
Revbump all Go packages after go116 update
   2021-03-19 18:37:10 by Benny Siegert | Files touched by this commit (215) | Package updated
Log message:
Revbump all Go packages after go115 update
   2021-01-23 15:23:16 by Benny Siegert | Files touched by this commit (209) | Package updated
Log message:
Revbump all Go packages after go115 update
   2020-12-04 10:25:33 by Benny Siegert | Files touched by this commit (5)
Log message:
New package, go-mod-0.4.0.

Ironically, this is not packaged as a Go module, because it is a dependency
of go-tools.

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.

Next | Query returned 7 messages, browsing 1 to 10 | previous