{"push_id":1031929432,"size":9,"distinct_size":9,"ref":"refs/heads/gentoo-zfs-0.6.5.4-release","head":"f37db47cf208891a388d5cd4ec2fe020a3344bcb","before":"88aefa02bd3a3c0fc8f8f194a819bb1514366d38","commits":[{"sha":"3041f8fcf38cb2d8a454d837d39978406f23a0b2","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"zfs_for_each: do not lose earlier errors after later successes","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/3041f8fcf38cb2d8a454d837d39978406f23a0b2"},{"sha":"fe560eac0bb41e646f303e13f1d725c26dc184a2","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"zfs_promote: conflicting snap does not have to be set\n\nE.g. if we try to promote a filesystem that is not a clone.","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/fe560eac0bb41e646f303e13f1d725c26dc184a2"},{"sha":"534987dbc458112aa821af64a79f140ae84bb0f1","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"zfs_stable_ioc_promote: fix unmounting of snapshots\n\ndmu_objset_find() expects a name that is a filesystem or volume\nname.  It gets confused if given a snapshot name.","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/534987dbc458112aa821af64a79f140ae84bb0f1"},{"sha":"5b9713cbd454cb2ef2e3723e8fa627109862ba02","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"zfs_iter_generic: do not treat ENOENT as an error\n\nFirst, this restores compatibility with historic behavior.\n\nSecond, this makes sense, because it is okay for datasets\nto get removed between when we decide to iterate them and\nwhen we actually attempt that.  In that case we behave as\nif the datasets didn't exist in the first place.  This is\nespecially useful when walking over complex dataset networks\nincluding children and clones (that can also be children).","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/5b9713cbd454cb2ef2e3723e8fa627109862ba02"},{"sha":"037324c9b36cf620cd97bea0ebabc755161a972c","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"lzc_* calls return *the* error code, errno is not it","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/037324c9b36cf620cd97bea0ebabc755161a972c"},{"sha":"7af5a70000326be9093922db06c0dc7d4107757d","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"if zfs list is called with both -r and -d, then -d should win","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/7af5a70000326be9093922db06c0dc7d4107757d"},{"sha":"0d241daf714ec117f6a8c53c20f189c769c57981","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"allow starting dataset to be filesystem or volume if depth is set","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/0d241daf714ec117f6a8c53c20f189c769c57981"},{"sha":"c7ff8ccb7ef315da87dec03ac68c36e1d8058cb9","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"set properties one by one only if we failed to set them at once\n\nPreviously the former was done even if the latter succeeded.","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/c7ff8ccb7ef315da87dec03ac68c36e1d8058cb9"},{"sha":"f37db47cf208891a388d5cd4ec2fe020a3344bcb","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"atomicity requirement matters only for setting multiple properties","distinct":true,"url":"https://api.github.com/repos/avg-I/zfs/commits/f37db47cf208891a388d5cd4ec2fe020a3344bcb"}]}