commit 5278e5cc50544ed7af28b15a1acd2b2e96a15a47
Author: Jojy Varghese <[email protected]>
Date: Tue Mar 15 17:12:01 2016 -0700
Added support for FTS_SLNONE in rmdir.
Review: https://reviews.apache.org/r/44874/
commit 5c4b348c8090ce61804b7701e3b0705ced975a7e
Author: Jojy Varghese <[email protected]>
Date: Tue Mar 15 17:11:54 2016 -0700
Added test for rmdir with device file.
Existing tests did not cover the case of removing directories with
special files like device files.
Review: https://reviews.apache.org/r/44873/
- Jie
On Tue, Mar 15, 2016 at 2:46 PM, Jie Yu <[email protected]> wrote:
> Also, I think we should fix the TODO in rmdir as well (i.e., handle
> FTS_SLNONE as well as Neil suggested).
>
> - Jie
>
> On Tue, Mar 15, 2016 at 2:39 PM, Jie Yu <[email protected]> wrote:
>>
>> Mesos currently has no notion of long term stable releases (i.e., LTS). I
>> think the consensus in the last community sync was to introduce LTS after
>> 1.0.
>>
>> 0.27.2 has already been released. Looks like we need 0.27.3 if we want to
>> backport it.
>>
>> I am OK with back porting it. Then the question is that whether we want to
>> backport it to other releases as well.
>>
>> - Jie
>>
>> On Tue, Mar 15, 2016 at 11:45 AM, Cong Wang <[email protected]>
>> wrote:
>>>
>>> Hi, all
>>>
>>> I don't know what is the process to request for a backport for Mesos
>>> stable releases and how Mesos community cares about stable releases.
>>> But... please consider to backport the following patch to at least
>>> 0.27 branch:
>>>
>>> https://reviews.apache.org/r/44230/
>>>
>>> It fixes a bug in our production which causes GC failed to prune a
>>> directory.
>>>
>>> The backport should be very straightforward. Please let me know if I
>>> can help anything.
>>>
>>> BTW, for Linux kernel we evaluate every bug fix to make sure it is
>>> backported to the right stable releases.
>>>
>>> Thanks.
>>
>>
>
