Very well then I just wnated the info for the conversation into my email. Seems not a good idea to do on the list. Seems better to do it this way. Nick On Wed, Jul 9, 2014 at 2:53 PM, Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote: > 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@xxxxxxxxxxxxxxx >>>> Cc: linux-kernel@xxxxxxxxxxxxxxx >>>> >>>> >>>> Hi all, >>>> >>>> Changes since 20140708: >>>> >>>> >>>> -- >>>> Cheers, >>>> Stephen Rothwell sfr@xxxxxxxxxxxxxxxx >>>> >>>> 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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
