All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Krause <xerofoify@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: Fwd: linux-next: Tree for Jul 9
Date: Wed, 9 Jul 2014 16:54:59 -0400	[thread overview]
Message-ID: <CAPDOMVjPv+-9J51xA1xYc6Wn=uf8xTibjeg+-ey4hRTuVA+pZg@mail.gmail.com> (raw)
In-Reply-To: <53BD9670.5030809@infradead.org>

On Wed, Jul 9, 2014 at 3:22 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 07/09/2014 11:56 AM, Nick Krause wrote:
>> 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
>>
>
> <see below>
>
>> On Wed, Jul 9, 2014 at 2:53 PM, Randy Dunlap <rdunlap@infradead.org> 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@vger.kernel.org
>>>>>> Cc: linux-kernel@vger.kernel.org
>>>>>>
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20140708:
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cheers,
>>>>>> Stephen Rothwell                    sfr@canb.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
>
> The mail thread is all here (just above here), so Reply does keep it,
> it's just at the bottom of the email instead of at the top.
> That's the way we prefer it, so please don't top-post your replies;
> move the text cursor to the bottom of the email and then begin typing.
>
> Thanks.
>
> --
> ~Randy


Ok Randy ,
Thanks for the help. Hope this message is better makes sense to me.
Cheers Nick

  reply	other threads:[~2014-07-09 20:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  8:31 linux-next: Tree for Jul 9 Stephen Rothwell
2014-07-09 17:07 ` Fwd: " Nick Krause
2014-07-09 17:11   ` Randy Dunlap
2014-07-09 17:13     ` Nick Krause
2014-07-09 18:47     ` Guenter Roeck
2014-07-09 18:53       ` Randy Dunlap
2014-07-09 18:56         ` Nick Krause
2014-07-09 19:22           ` Randy Dunlap
2014-07-09 20:54             ` Nick Krause [this message]
2014-07-10  9:43               ` Bernd Petrovitsch
2014-07-10 17:08                 ` Nick Krause
     [not found]               ` <53BDBC22.7050009@infradead.org>
2014-07-10 17:10                 ` Nick Krause
2014-07-11  5:19                   ` Nick Krause

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPDOMVjPv+-9J51xA1xYc6Wn=uf8xTibjeg+-ey4hRTuVA+pZg@mail.gmail.com' \
    --to=xerofoify@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.