[brasero] Created tag BRASERO_2_28_2



The unsigned tag 'BRASERO_2_28_2' was created.

Tagger: Philippe Rouquier <bonfire-app wanadoo fr>
Date: Mon Oct 19 19:51:38 2009 +0200

    Tagged for 2.28.2 release

Changes since the last tag 'BRASERO_2_28_1':

Aron Xu (1):
      Fixed a small typo.

Leonid Kanter (1):
      Updated Russian translation by Dmitry Koroban <dmitry koroban gmail com>

Lucian Adrian Grijincu (1):
      Updated Romanian translation

Milo Casagrande (1):
      Updated Italian translation

Philippe Rouquier (36):
      Allow all characters to be part of Volume and Volset identifiers in the Primary Volume Descriptor
      Make two internal functions public
      Make some private functions public
      Remove unneeded code
      API clarification
      Let BraseroProcess derived plugins add a track of their own and if so don't automatically add one
      Revert "Let BraseroProcess derived plugins add a track of their own and if so don't automatically add one"
      Wrong branch
      Wrong branch
      Fix #597584 -  make burning audio cds with brasero work
      Fix #598306 -  brasero crashed with SIGSEGV in brasero_burn_session_set_image_output_full()
      Fix #597808 -  Crash when launching with -e option
      Fix #598149 -  Remember volume title
      Fix #598908 -  data project: multiple file rename do not work
      Fix forgotten unref that left BraseroBurnSession with one ref and therefore all temp files after a burning
      Remove useless operation
      Check flags _before_ trying to create a task
      Also check whether the drive is probing when checking whether there is something inside
      when BraseroBurn objects go to sleep (waiting something), check the return value in case we were cancelled in the mean time
      Add a new error code
      Small fix for a wrong variable used
      Fix leaking of GDrive object
      Instead of waiting for the end of the probing thread cancel it if a new probe is required
      Don't let anything (except a final unref) interrupt the initial thread that initializes the drive capabilities
      While we ask for a reprobe of the drive contents, wait for it to be finished before going on
      Avoid in rare cases (using valgrind mostly) to set error twice for GIO operations
      When updating the GDrive object associated with the BraseroDrive make sure that priv->gdrive is properly set if gdrive is NULL and cancel any ongoing GIO operation
      Add an additional reference to GDrive or GVolume when doing an operation on them in case the GDrive or the GVolume object gets updated while waiting in the main loop
      When eject operation is cancelled with GDrive don't try to eject with a GVolume
      Remove useless line
      Add a new function brasero_drive_is_locked ()
      Remove useless code
      Wait for the drive to complete probing before ejecting or returning from brasero_burn_reprobe
      Don't use gtk_widget_show () on the dialog until it has been filled with contents.
      Updated NEWS
      Bumped version to 2.28.2



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]