guix_mirror_bot pushed a change to branch kernel-updates
in repository guix.
discard 3de44db926 gnu: linux-libre 5.15: Update to 5.15.188.
discard fe5e783ab1 gnu: linux-libre 6.1: Update to 6.1.145.
discard d83ea86267 gnu: linux-libre 6.6: Update to 6.6.98.
discard d5e72a4eeb gnu: linux-libre 6.12: Update to 6.12.38.
discard a0bdb72b02 gnu: linux-libre: Update to 6.15.6.
new eeb6831735 gnu: linux-libre: Update to 6.15.6.
new 59ea8e7247 gnu: linux-libre 6.12: Update to 6.12.38.
new 6dbc99ca6d gnu: linux-libre 6.6: Update to 6.6.98.
new 18402a59ea gnu: linux-libre 6.1: Update to 6.1.145.
new 4d4009e587 gnu: linux-libre 5.15: Update to 5.15.188.
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 (3de44db926)
\
N -- N -- N refs/heads/kernel-updates (4d4009e587)
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:
gnu/packages/linux.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
