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] [day] [month] [year] [list]
Message-ID: <CA+55aFwX+aXbtGeNUFJF_fpZJroefSY0E63Cx2OyodyGkH1j=A@mail.gmail.com>
Date:	Sat, 12 Apr 2014 12:38:28 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Eric Paris <eparis@...hat.com>
Cc:	linux-audit@...hat.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Audit subsystem for v3.15

On Thu, Apr 10, 2014 at 4:53 PM, Eric Paris <eparis@...hat.com> wrote:
>
> Please pull the audit tree for v3.15.  You will have merge conflicts.

The merge conflicts were easy to resolve. I appreciate you spending
the time to explain them, but quite frankly, I can figure out trivial
ones on my own. What I really really need is to know what the hell the
pull request *does*, and why I should pull this.

So now I've done the merge, and find myself considering just undoing
it again, because there is no explanation for what the hell I pulled
in.

I ended up looking at all the commits and being mightily annoyed by
this all. I guess I'll let it go now, but in general, if I get pull
requests that don't even bother to explain why I should pull and what
the point of it all is, I'm going to start ignoring them.

             Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ