This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/palves/ctrl-c in repository binutils-gdb.
discards fedd20e7bcc Document pseudo-terminal and interrupting changes discards d4105ffb00a GNU/Linux: Interrupt/Ctrl-C with SIGSTOP instead of SIGINT [...] discards c907018cd6f convert previous_inferior_ptid to strong reference to thread_info discards 41a24e263f8 exists_non_stop_target: Avoid flushing frames discards d48337d7bfe Always put inferiors in their own terminal/session [gdb/942 [...] new d9bda172522 Always put inferiors in their own terminal/session [gdb/942 [...] new de89924a63b exists_non_stop_target: Avoid flushing frames new 86a57987361 convert previous_inferior_ptid to strong reference to thread_info new 814fb49ba38 GNU/Linux: Interrupt/Ctrl-C with SIGSTOP instead of SIGINT [...] new 4e18fe9cb3f Document pseudo-terminal and interrupting changes
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 (fedd20e7bcc) \ N -- N -- N refs/heads/users/palves/ctrl-c (4e18fe9cb3f)
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 5 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: