This is an automated email from the git hooks/post-receive script.
agruenba pushed a change to branch agruenba-extents
in repository gfs2-utils.
discard 1da6566a fsck.gfs2: Convert enum values to upper-case
discard 322f821c fsck.gfs2: Add partial extent-based inode support
new d4e52f2c fsck.gfs2: Convert enum values to upper-case
new 963e9001 fsck.gfs2: Add partial extent-based inode support
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 (1da6566a)
\
N -- N -- N refs/heads/agruenba-extents (963e9001)
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 2 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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
Show replies by date