Don't use -S creation order in zfs snapshot listings

This fixes problems when using -R replications.

In a scenario where in the same timestamp two or more snapshots were
created for a dataset, the replication could fail, because when checking
the remote side, another snapshots might get replicated, and due to the
ordering bad results came back.

Example:
~# zfs snapshot test@a && zfs snapshot test@b && sleep 1 && zfs snapshot test@c
~# zfs list -t snapshot -d 1 -H -o name test
test@a
test@b
test@c
~# zfs list -t snapshot -d 1 -H -o name -s creation test
test@a
test@b
test@c
~# zfs list -t snapshot -d 1 -H -o name -S creation test
test@c
test@a
test@b

As shown, the reverse ordering, or maybe any ordering breaks zfs
snapshot dependencies in the listing.
Fix for listing snapshots in a special case
Allow decimal argument for interval
Merge pull request #6 from rkojedzinszky/master

Fix for recursive replication with multiple snapshot schedules
tail should be used here as we use native (txg) ordering and wants
the last snapshot at the remote end.
Add lz4 in zfs compression choices
Merge pull request #8 from rkojedzinszky/master

Add lz4 in zfs compression choices
Auto-Commit of i18n data from Pootle for GUI
Merge pull request #2 from freenas/master

Merge latest changes