This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/clyon/gdb-7.5-fdpic in repository binutils-gdb.
discards be9914dcb5f ARM/FDPIC: Add core file support discards 4217001bca1 ARM/FDPIC: Add support to unwind thumb2 signal trampoline discards d911b6eaf03 ARM/FDPIC: Allow backtrace to cross signal handler discards 7f609a33f75 ARM/FDPIC: Add support for GDB call command discards 30b6d431686 ARM/FDPIC: Add GDB support discards 28cdfaf40f4 ARM/FDPIC: Add gdbserver support adds 94fcbd86840 ARM/FDPIC: Add gdbserver support adds 22e43d2b35c ARM/FDPIC: Add GDB support adds 82934b09cd4 ARM/FDPIC: Add support for GDB call command adds 666c20f65eb ARM/FDPIC: Allow backtrace to cross signal handler adds d5c137cf529 ARM/FDPIC: Add support to unwind thumb2 signal trampoline adds 4fbda0f249e ARM/FDPIC: Add core file 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 (be9914dcb5f) \ N -- N -- N refs/heads/users/clyon/gdb-7.5-fdpic (4fbda0f249e)
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.
No new revisions were added by this update.
Summary of changes: