This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/lsix/refactor-typesafe-var in repository binutils-gdb.
discards d57fcb8bba5 Introduce user provided setter and getter function for setting discards fa31cda74a6 gdb: make string-like set show commands use std::string variable discards 7c8af42de01 Add typesafe getter/setter for cmd_list_element.var new 1e35da4a7e7 Add typesafe getter/setter for cmd_list_element.var new dd4b9dd2b26 gdb: make string-like set show commands use std::string variable new 743201dc1a7 Introduce user provided setter and getter function for params
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 (d57fcb8bba5) \ N -- N -- N refs/heads/users/lsix/refactor-typesafe-var (743201dc1a7)
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 3 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: gdb/cli/cli-decode.c | 353 +++++++++++++++++++++++++++++++++++++++++++++++---- gdb/command.h | 104 ++++++++++++++- 2 files changed, 425 insertions(+), 32 deletions(-)