lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 10 Sep 2018 18:06:33 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Ville Syrjälä <ville.syrjala@...ux.intel.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>,
        Dou Liyang <douly.fnst@...fujitsu.com>,
        Pavel Tatashin <pasha.tatashin@...rosoft.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] Revert "x86/tsc: Consolidate init code"

On Mon, Sep 10, 2018 at 06:51:13PM +0300, Ville Syrjälä wrote:
> Sounds to me like the maintainer should figure out how to delegate some
> of the load a bit. Or just go on vacation and ignore all mails. I hear
> stress isn't good for you.

Bullshit.

> That's what all patches are. No should be applying unreviewed patches
> blindly.
> 
> Also often a revert is a perfect way to handle regressions. It gets
> the angry users off your back ASAP allowing you to fix the bug

More bullshit.

> Calm down. No one is out to revert all your patches.

Even more bullshit.

> Maybe you can propose a new git-regression tool then? And document that
> you want bugs reported using it? Ideally I'd say it should do almost
> exactly what git revert does except s/revert/regression/. Though I
> suppose it could include the original diff instead of the reverse.

Even even more bullshit.

> Now, how about we stop this pointless "logic" discussion and
> focus on the techinal stuff from now on?

That's the only constructive and serious thing you've said so far.
Let's.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ