This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/hjl/linux/master in repository binutils-gdb.
discards c40667e624 Update support for R_X86_64_THUNK_GOTPCRELX discards b27a710f0e Fix ""x86-64: Generate branch with PLT32 relocation" discards aecc4a249f Apply "x86-64: Generate branch with PLT32 relocation" new c22c7018f7 Apply "x86-64: Generate branch with PLT32 relocation" new aadfd1e188 Update support for R_X86_64_THUNK_GOTPCRELX
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 (c40667e624) \ N -- N -- N refs/heads/users/hjl/linux/master (aadfd1e188)
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 "omits" are not gone; other references still refer to them. Any revisions marked "discards" 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 "adds" were already present in the repository and have only been added to this reference.
Summary of changes: