commit 238dbbd64daa54e942758c240417db0cebfb9c65
Author: Ondrej Holy <oholy@redhat.com>
Date:   2016-04-11

    Update NEWS for 1.28.1 release

M	NEWS

commit c43370a9a5040b33656602fa2eb2a791a0df74ff
Author: Piotr Drąg <piotrdrag@gmail.com>
Date:	2016-04-07

    Updated Polish translation

M	po/pl.po

commit beea21e124d95c2f7cc0130148084e5e86eb46e5
Author: Ondrej Holy <oholy@redhat.com>
Date:	2016-03-24

    udisks2: Abort mount operation if volume is unlocked

    Mount operation for encrypted volumes consists from two udisks2 calls
    (unlock and mount). Volume monitor is able to mount already unlocked
    volumes. However password prompt doesn't disappear if the volume is
    unlocked externally and any reaction causes mount operation failure.
    The volume may be unlocked externally by e.g. project Tang, see
    https://github.com/latchset/tang for more details. Abort mount
    operation and continue with mounting in such situations.

    https://bugzilla.gnome.org/show_bug.cgi?id=763890

M	monitor/udisks2/gvfsudisks2volume.c

commit dd98c02ecde5cc081a2d0e3990780efe3d66edfa
Author: Ondrej Holy <oholy@redhat.com>
Date:	2016-03-24

    udisks2: Lock unlocked volumes on eject/stop

    The eject/stop operation fails currently with "Cannot eject drive in
    use: Encrypted device /dev/sdb1 is unlocked" if any volume is unlocked
    and isn't mounted. The volume monitor is able to mount already
    unlocked
    volumes, so it should be able to eject unlocked volumes also. Lock the
    unlocked volumes if there are any before eject/stop operation.

    https://bugzilla.gnome.org/show_bug.cgi?id=763890

M	monitor/udisks2/gvfsudisks2drive.c

commit 8d3f2c6d7079e10fd34d73505cc28e5f449ce217
Author: Shi Jing <jingshi@ubuntukylin.com>
Date:	2016-04-06

    Update zh_CN translation

M	po/zh_CN.po

commit be29e48e0d90453e115dd1096460ddef8296c8e6
Author: Ondrej Holy <oholy@redhat.com>
Date:	2016-03-09

    trash: Check modification time to avoid rereading

    Rereading of trash dirs is pretty expensive and unfortunately it is
    performed more often with recent changes. Check modification time of
    each trash dir in order to avoid needless rereading, because simple
    query_info call is much faster than enumeration.

    https://bugzilla.gnome.org/show_bug.cgi?id=711459

M	daemon/trashlib/trashdir.c

commit 7d0ef03610164e80d15897134d82a8e82bd006a3
Author: Ondrej Holy <oholy@redhat.com>
Date:	2016-03-15

    trash: Rescan trash dirs before operations with files

    Patches to use G_FILE_ATTRIBUTE_TRASH_ITEM_COUNT were recently
    proposed
    for Nautilus and GTK+. We have to be sure that the item count is valid
    and therefore we have to rescan the trash dirs before. Otherwise the
    count is 0 if enumeration isn't called before, which is obviously
    wrong.
    Similarly, trash dirs have to be rescanned before other operations
    (i.e. read, delete, pull), otherwise the operations may fail with
    G_IO_ERROR_NOT_FOUND if enumeration wasn't called before.

    https://bugzilla.gnome.org/show_bug.cgi?id=711459

M	daemon/gvfsbackendtrash.c

commit 116fc113fbb58363fb81b3114c348c3945fefa65
Author: Trần Ngọc Quân <vnwildman@gmail.com>
Date:	2016-03-27

    Updated Vietnamese translation

    Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>

M	po/vi.po

commit 365151ebbc8209fc6c6662dc38e312380818d7f3
Author: Inaki Larranaga Murgoitio <dooteo@zundan.com>
Date:	2016-03-23

    Updated Basque language

M	po/eu.po

commit ab6b98e266fc725a88ba060c06133738266e2218
Author: Ondrej Holy <oholy@redhat.com>
Date:	2016-03-21

    Post release version bump

M	configure.ac