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 1a21f3bf406 [WIP] Introduce user provided setter and getter function fo [...] discards 46825a3579a gdb: make string-like set show commands use std::string variable discards 30ac1f31fb0 Add typesafe getter/setter for cmd_list_element.var new 2d606981ef2 Add typesafe getter/setter for cmd_list_element.var new b8c7e3b4a5f gdb: make string-like set show commands use std::string variable new 6472eba3351 [WIP] Introduce user provided setter and getter function fo [...]
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 (1a21f3bf406) \ N -- N -- N refs/heads/users/lsix/refactor-typesafe-var (6472eba3351)
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-cmds.c | 59 ++++++++++++++++++++++++++------------------------- gdb/cli/cli-setshow.c | 2 +- 2 files changed, 31 insertions(+), 30 deletions(-)