From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: Nick Krause <xerofoify@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
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: Thu, 10 Jul 2014 11:43:27 +0200 [thread overview]
Message-ID: <1404985410.12451.3.camel@thorin> (raw)
In-Reply-To: <CAPDOMVjPv+-9J51xA1xYc6Wn=uf8xTibjeg+-ey4hRTuVA+pZg@mail.gmail.com>
Hi!
On Mit, 2014-07-09 at 16:54 -0400, Nick Krause wrote:
[... useless quotes deleted ...]
> Thanks for the help. Hope this message is better makes sense to me.
And always quoting everything is bad mail style too - just quote just
the relevant parts for the answer, not more, not less.
Everyone keeps the last mails from the thread around and they also can
be founds in public archives.
Bernd
--
"I dislike type abstraction if it has no real reason. And saving
on typing is not a good reason - if your typing speed is the main
issue when you're coding, you're doing something seriously wrong."
- Linus Torvalds
next prev parent reply other threads:[~2014-07-10 9:44 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
2014-07-10 9:43 ` Bernd Petrovitsch [this message]
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=1404985410.12451.3.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--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 \
--cc=xerofoify@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox