Fixes since v1.7.10.4
---------------------
* "git fast-export" did not give a readable error message when the
same mark erroneously appeared twice in the --import-marks input.
* "git rebase -p" used to pay attention to rebase.autosquash which
was wrong. "git rebase -p -i" should, but "git rebase -p" by
itself should not.
(ok agc@ to commit during freeze)
the same reason: gcc "knows" that malloc has no side effects and
reorders code around it, only it's wrong. Fixes SIGSEGV during build
seen in some environments.
Bump package revision as a precaution, because I don't understand why
this sometimes doesn't fail and sometimes does with the same gcc
version.
===========================
Fixes since v1.7.10.3
---------------------
* The message file for Swedish translation has been updated a bit.
* A name taken from mailmap was copied into an internal buffer
incorrectly and could overun the buffer if it is too long.
* A malformed commit object that has a header line chomped in the
middle could kill git with a NULL pointer dereference.
* An author/committer name that is a single character was mishandled
as an invalid name by mistake.
* The progress indicator for a large "git checkout" was sent to
stderr even if it is not a terminal.
* "git grep -e '$pattern'", unlike the case where the patterns are
read from a file, did not treat individual lines in the given
pattern argument as separate regular expressions as it should.
* When "git rebase" was given a bad commit to replay the history on,
its error message did not correctly give the command line argument
it had trouble parsing.
Also contains minor fixes and documentation updates.
2.5.0 - 2012-06-06
It's a bug fix release.
Fixes
* Fixed a backward incompatibility of TestUnitMediator#run_suite introduced
in 2.4.9. [GitHub#28] [Reported by Vladislav Rassokhin]
Thanks
* Vladislav Rassokhin
2.4.9 - 2012-06-03
It's a bug fix release.
Improvements
* Test::Unit.run? -> Test::Unit::AutoRunner.need_auto_run?. Test::Unit.run?
is marked as deprecated but it is still available.
* [experimental] Added top level "run" method for "ruby -rtest-unit -e run
test/test_*.rb". Is this API OK or dirty?
* Made failure output more readable on no color mode.
* Supported showing ASCII-8BIT diff in failure message.
* [ui][console] Supported ENV["TERM"] == "xterm-256color" as color available
terminal. [GitHub#26] [Reported by Michael Grosser]
* [ui][console] Supported "-256color" suffix ENV["TERM"] terminal as 256
color supported terminal.
Fixes
* Fixed a bug that --workdir doesn't work.
* Consumed processed command line parameters in ARGV as --help
says. [RubyForge#29554] [Reported by Bob Saveland]
* Added missing require "test/unit/diff". [GitHub#25] [Reported by Stephan
Kulow]
Thanks
* Bob Saveland
* Stephan Kulow
* Michael Grosser
with at-spi-atk. It makes the assumption that at-spi2-atk is used with
gtk3 only.
2.5.2:
* Fix for bug 677211 - The collection interface's MATCH_ANY fails for states
2.3.91:
* Have GetIndexInParent() return a signed int, per the spec.
* Send a DoAction reply message before invoking atk (works around
atk_action_do_action potentially not returning right away for gtk).
2.3.90:
* Have GrabFocus return a bool, per the spec, rather than a uint32.
* Fix a potential crash when emitting a signal if the ATK implementor
misbehaves.
New/updated Khmer, Malayalam, Norwegian Nynorsk, Hindi translations
2.5.2:
* Fix a crash when a call to fetch a hyperlink times out.
* Fix C++ compilation.
* Remove a warning that was sometimes logged when a method call timed out.
* Fix crash in atspi_deregister_keystroke_listener (FDO#50578)
2.5.1:
* Add atspi_set_timeout.
* By default, disable method call timeouts until an application
has been on the bus for 15 seconds (work-around for applications
with potentially long start-up times). This behavior can be changed
with a call to atspi_set_timeout.
* Fix GError sent when receiving a reply of the wrong type
* Fix typo in atspi_document_get_attribute_value
* Fix for bug 675004 - object:state-changed:defunct events are
emitted as object:state-change:defunct
2.4.0:
* Fix typo in at-spi-dbus-bus.desktop.in (BGO#605662).
2.3.92:
* Some changes to try to prevent at-spi2-registryd from incorrectly
thinking that an AT is hung and passing keys meant for it to the application.
* Fix crash fetching an error from a reply when retrieving a property.
2.3.91:
* Invalidate states when receiving a focus event (BGO#663992).
* Fix atspi_table_get_row_column_extents_at_index.
* Expect a signed int for GetIndexInParent, per the spec.
* Send key events to listeners assumed to be hung, but don't block.
* Reduce the method call timeout slightly, so that it will be lower than
the keystroke listener timeout.
* Don't cache data for transient objects.
* Enable caching on a call to atspi_accessible_set_cache_mask, even if
atspi-event_main() hasn't been called.
2.3.90:
* At-spi-bus-launcher now emits PropertiesChanged signals from the correct
interface.
* If a keystroke listener does not respond, disable it until it responds.
This prevents the desktop from locking up if an AT hangs or is suspended
and has a keyboard listener registered.
* Fix a warning when a NULL object is returned as the detail of an event.
Other than the upgrade itself, this also adds a new 'tests' option to
the package to indicate whether the Kyua-specific tests should be built
or not. I do not recommend disabling their build, but not specifiying
the 'tests' option cuts down the build time significantly.
The major changes since 0.3 are:
* Added the 'report-html' command to generate HTML reports of the
execution of any recorded action.
* Changed the '--output' flag of the 'report' command to only take a
path to the target file, not its format. Different formats are better
supported by implementing different subcommands, as the options they
may receive will vary from format to format.
* Added a '--with-atf' flag to the configure script to control whether
the ATF tests get built or not. May be useful for packaging systems
that do not have ATF in them yet. Disabling ATF also cuts down the
build time of Kyua significantly, but with the obvious drawbacks.
* Grouped 'kyua' subcommands by topic both in the output of 'help' and
in the documentation. In general, the user needs to be aware of
commands that rely on a current project and those commands that rely
purely on the database to generate reports.
* Made 'help' print the descriptions of options and commands properly
tabulated.
* Changed most informational messages to automatically wrap on screen
boundaries.
* Rewrote the configuration file parsing module for extensibility. This
will allow future versions of Kyua to provide additional user-facing
options in the configuration file.
No syntax changes have been made, so existing configuration files
(version 1) will continue to be parsed without problems. There is one
little exception though: all variables under the top-level
'test_suites' tree must be declared as strings.
Similarly, the '-v' and '--variable' flags to the command line must
now carry a 'test_suites.' prefix when referencing any variables under
such tree.
