-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/03/12 16:16, Alon Bar-Lev wrote:
> The only component that is in question is lzo. I still think this is
> packager responsibility, not sure why this is an exception. But if it
> will make people happy, I will enable lzo by default. All the other
On Thu, Mar 22, 2012 at 1:45 PM, David Sommerseth
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 19/03/12 16:16, Alon Bar-Lev wrote:
>> The only component that is in question is lzo. I still think this is
>> packager responsibility, not sure why this is an exception. But if it
>>
On Thu, Mar 22, 2012 at 1:47 PM, Alon Bar-Lev wrote:
> On Thu, Mar 22, 2012 at 1:45 PM, David Sommerseth
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 19/03/12 16:16, Alon Bar-Lev wrote:
>>> The only component that is in question is lzo. I still think this is
>>> packager
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/03/12 12:47, Alon Bar-Lev wrote:
> On Thu, Mar 22, 2012 at 1:45 PM, David Sommerseth
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 19/03/12 16:16, Alon Bar-Lev wrote:
>>> The only component that is in question is lzo. I st
No.
Please don't take the patches from the mailing list.
As I explicitly requested in the past *SEVERAL* times.
I've done minor fixups in my repository.
As you see my work is in good quality and without comments, issues I
fixed needs to be fixed in tree as well.
As I requested this approach sever
Hello,
I will try to rephrase this in different angle as well.
During the time you made a review and found no issues, I took the time
for reviewing my own code and further test, and I found issues to be
fixed, sent the patches to me back to review.
Just think of it as another developer would hav
