This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/mark/try-gdbarch_tdep_cast in repository binutils-gdb.
discards 0aba3fb019e Rename gdbarch_tdep template function to gdbarch_tdep_cast [...] adds 4c70437ddc9 Automatic date update in version.in adds 561e83f7c5c Automatic date update in version.in adds c444385fad2 gdb/testsuite: rename get_maint_bp_addr and move it to gdb- [...] adds ea892bdc4b6 gdb/testsuite: add a clear test to py-breakpoint.exp adds c88bac870f1 Add a header to bfd/README new 7cf3e8b5ca2 Rename gdbarch_tdep template function to gdbarch_tdep_cast [...]
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 (0aba3fb019e) \ N -- N -- N refs/heads/users/mark/try-gdbarch_tdep_cast (7cf3e8b5ca2)
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 1 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: bfd/README | 2 ++ bfd/version.h | 2 +- gdb/testsuite/gdb.base/clear_non_user_bp.exp | 25 +------------------------ gdb/testsuite/gdb.python/py-breakpoint.exp | 20 ++++++++++++++++++++ gdb/testsuite/lib/gdb-utils.exp | 28 ++++++++++++++++++++++++++++ 5 files changed, 52 insertions(+), 25 deletions(-)