This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch users/simark/refactor-typesafe-var in repository binutils-gdb.

discards 002e0066dee gdb: Setting setter return a bool to tell if the value changed discards d712b28cc22 gdb: Have setter and getter callbacks for settings discards d1b02ba788e gdb: make string-like set show commands use std::string variable discards 7812fc6a3d8 gdb: Add typesafe getter/setter for cmd_list_element.var new 5be5fa3ffd2 gdb: Add typesafe getter/setter for cmd_list_element.var new fc1987599f5 gdb: make string-like set show commands use std::string variable new bb1509a2250 gdb: Have setter and getter callbacks for settings new 8d26838e40a gdb: Setting setter return a bool to tell if the value changed

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 (002e0066dee) \ N -- N -- N refs/heads/users/simark/refactor-typesafe-var (8d26838e40a)

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 4 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/guile/scm-param.c | 5 ++++- gdb/python/py-param.c | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-)