linux-kernel - Re: Fwd: linux-next: Tree for Jul 9

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]

Message-ID: <53BD8F8E.9030105@infradead.org>
Date:	Wed, 09 Jul 2014 11:53:02 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Guenter Roeck <linux@...ck-us.net>
CC:	Nick Krause <xerofoify@...il.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>
Subject: Re: Fwd: linux-next: Tree for Jul 9

On 07/09/2014 11:47 AM, Guenter Roeck wrote:
> On Wed, Jul 09, 2014 at 10:11:40AM -0700, Randy Dunlap wrote:
>> On 07/09/2014 10:07 AM, Nick Krause wrote:
>>> ---------- Forwarded message ----------
>>> From: Stephen Rothwell wrote on Wed, Jul 9, 2014 at 4:31 AM
>>> Subject: linux-next: Tree for Jul 9
>>> To: linux-next@...r.kernel.org
>>> Cc: linux-kernel@...r.kernel.org
>>>
>>>
>>> Hi all,
>>>
>>> Changes since 20140708:
>>>
>>>
>>> --
>>> Cheers,
>>> Stephen Rothwell                    sfr@...b.auug.org.au
>>>
>>> Hey Stephen,
>>>
>>> A lot of your builds that are failing seem to build for me. Please try
>>> a compiler toolchain
>>> newer then gcc 4.6.3 to see if this is why your builds are failing.
>>> Since all the arm builds
>>> you have failing build for me.
>>> Cheers Nick
>>>
>>
>> Hey Nick,
>>
>> Does your email client interface have a "Reply All" or "Reply to All" button
>> or selection that you can use?  Please use that instead of Forwarding each message.
>> That will make it easier to read the email threading.
>>
> I suspect he may be using an e-mail client from a certain vendor in Redmond, WA.
> It appears they have not heard that there is something like '>' to mark original
> text in e-mail replies.

He used Reply one time and then reverted back to his old ways.

Nick, the idea is to use Reply all the time, not just one time.
That is, if you want to do things correctly and are not just wasting our time.

-- 
~Randy
--
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/