Re: [FYI] tux3: Core changes

[Elifarley Callado Coelho Cruz <elifarley@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2455 bytes --]

My gosh!!!! This is driving me crazy. Please let's make it crystal clear,
in technical and precise terms, devoid of any ad hominem attacks or the
like, what is preventing Tux3 from being merged.

Maybe a list of issues in Github, so that each issue can be scrutinized
more easily. Like this one: https://github.com/tux3fs/tux3-merging/issues/1

Daniel, thank you so much for spending so much energy to fight not only for
tux3, but for logic, reason and rationality, and for a saner dev process in
Linux.

Elifarley Cruz

-

 " Do not believe anything because it is said by an authority, or if it  is
said to come from angels, or from Gods, or from an inspired source.
Believe it only if you have explored it in your own heart and mind and body
and found it to be true.  Work out your own path, through diligence."
- Gautama Buddha

On Fri, Jul 31, 2015 at 7:27 PM, David Lang <david@lang.hm> wrote:

> On Fri, 31 Jul 2015, Daniel Phillips wrote:
>
> On Friday, July 31, 2015 11:29:51 AM PDT, David Lang wrote:
>>
>>> We, the Linux Community have less tolerance for losing people's data and
>>> preventing them from operating than we used to when it was all tinkerer's
>>> personal data and secondary systems.
>>>
>>> So rather than pushing optimizations out to everyone and seeing what
>>> breaks, we now do more testing and checking for failures before pushing
>>> things out.
>>>
>>
>> By the way, I am curious about whose data you think will get lost
>> as a result of pushing out Tux3 with a possible theoretical bug
>> in a wildly improbable scenario that has not actually been
>> described with sufficient specificity to falsify, let alone
>> demonstrated.
>>
>
> you weren't asking about any particular feature of Tux, you were asking if
> we were still willing to push out stuff that breaks for users and fix it
> later.
>
> Especially for filesystems that can loose the data of whoever is using it,
> the answer seems to be a clear no.
>
> there may be bugs in what's pushed out that we don't know about. But we
> don't push out potential data corruption bugs that we do know about (or
> think we do)
>
> so if you think this should be pushed out with this known corner case
> that's not handled properly, you have to convince people that it's _so_
> improbable that they shouldn't care about it.
>
> David Lang
>
>
> _______________________________________________
> Tux3 mailing list
> Tux3@phunq.net
> http://phunq.net/mailman/listinfo/tux3
>

[-- Attachment #1.2: Type: text/html, Size: 3633 bytes --]

[-- Attachment #2: Type: text/plain, Size: 120 bytes --]

_______________________________________________
Tux3 mailing list
Tux3@phunq.net
http://phunq.net/mailman/listinfo/tux3