From mboxrd@z Thu Jan 1 00:00:00 1970 From: Elifarley Callado Coelho Cruz Subject: Re: [FYI] tux3: Core changes Date: Sat, 1 Aug 2015 07:55:45 -0300 Message-ID: References: <67294911-1776-46b8-916d-0e5642a38725@phunq.net> <20150526070910.GA3307@quack.suse.cz> <20150526090058.GA8024@quack.suse.cz> <5564D60E.6000306@phunq.net> <20150527084138.GD2590@quack.suse.cz> <87a8vtdqfz.fsf@mail.parknet.co.jp> <20150623161247.GP2427@quack.suse.cz> <87k2ueepd6.fsf@mail.parknet.co.jp> <20150709160528.GK2900@quack.suse.cz> <874mklaqbn.fsf@mail.parknet.co.jp> <1981a91e-30a9-43ce-9a05-14aa777e46a5@phunq.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1619177128==" Cc: Rik van Riel , Jan Kara , tux3@tux3.org, Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, Daniel Phillips , OGAWA Hirofumi To: David Lang Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tux3-bounces@phunq.net Sender: "Tux3" List-Id: linux-fsdevel.vger.kernel.org --===============1619177128== Content-Type: multipart/alternative; boundary=001a1135b7909d88da051c3dc941 --001a1135b7909d88da051c3dc941 Content-Type: text/plain; charset=UTF-8 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 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 > --001a1135b7909d88da051c3dc941 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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

M= aybe a list of issues in Github, so that each issue can be scrutinized more= easily. Like this one:=C2=A0https://github.com/tux3fs/tux3-merging/issu= es/1

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


Elifarley Cruz

-

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

On Fri, Jul 31, 2015 at 7:27 PM, David Lang = <da= vid@lang.hm> wrote:
O= n 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 an= d preventing them from operating than we used to when it was all tinkerer&#= 39;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 ou= t.

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 i= t 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. Bu= t we don't push out potential data corruption bugs that we do know abou= t (or think we do)

so if you think this should be pushed out with this known corner case that&= #39;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

--001a1135b7909d88da051c3dc941-- --===============1619177128== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Tux3 mailing list Tux3@phunq.net http://phunq.net/mailman/listinfo/tux3 --===============1619177128==--