guix_mirror_bot pushed a change to branch go-team
in repository guix.
discard b30c50f37c gnu: go-github-com-imdario-mergo: Use default go.
discard 7fa3778d3e gnu: go-github-com-darccio-mergo: Use default go.
discard 9ea16ca837 gnu: go-github-com-onsi-gomega: Run vet tests.
discard 308147b62c gnu: go-github-com-coreos-go-systemd-v22: Update to 22.7.0.
discard 46fb6733d2 gnu: go-github-com-warpfork-go-wish: Build with default go.
discard ed9599c90b gnu: go-github-com-warpfork-go-wish: Update to 0.12.1.
new 3daa05b74c gnu: go-github-com-warpfork-go-wish: Build with default go.
new b1e2b91728 gnu: go-github-com-coreos-go-systemd-v22: Update to 22.7.0.
new e07322130a gnu: go-github-com-onsi-gomega: Run vet tests.
new 76f0e2a5e7 gnu: go-github-com-darccio-mergo: Use default go.
new cf458a11ac gnu: go-github-com-imdario-mergo: Use default go.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (b30c50f37c)
\
N -- N -- N refs/heads/go-team (cf458a11ac)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
