public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 4/8] docs: fix ManagementStyle book name
Date: Thu, 09 Oct 2008 16:52:35 -0700	[thread overview]
Message-ID: <12235963552413@xenotime.net> (raw)
In-Reply-To: <12235963551043@xenotime.net>

From: Jiri Pirko <jpirko@redhat.com>

Just corrected the book name. I'm probably the only one who ever read
this file :-)

Signed-off-by: Jiri Pirko <jpirko@redhat.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 Documentation/ManagementStyle |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-2.6.27-rc9-git2.orig/Documentation/ManagementStyle
+++ linux-2.6.27-rc9-git2/Documentation/ManagementStyle
@@ -17,7 +17,7 @@ companies.  If you sign purchase orders 
 budget of your group, you're almost certainly not a kernel manager. 
 These suggestions may or may not apply to you. 
 
-First off, I'd suggest buying "Seven Habits of Highly Successful
+First off, I'd suggest buying "Seven Habits of Highly Effective
 People", and NOT read it.  Burn it, it's a great symbolic gesture. 
 
 (*) This document does so not so much by answering the question, but by


-- 


  parent reply	other threads:[~2008-10-09 23:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 23:52 [PATCH 1/8 for 2.6.27] docs: fix uvesafb mode_option Randy Dunlap
2008-10-09 23:52 ` [PATCH 7/8] docs: fix Doc/x86/ subdir references Randy Dunlap
2008-10-09 23:52 ` Randy Dunlap [this message]
2008-10-09 23:52 ` [PATCH 8/8] docs: fix docbook cmd output alignment Randy Dunlap
2008-10-09 23:52 ` [PATCH 5/8] docs: add printk lib. extensions Randy Dunlap
2008-10-09 23:52 ` [PATCH 6/8] docs: add URL for paper on submitting patches Randy Dunlap
2008-10-09 23:52 ` [PATCH 3/8] docs: fix ramfs hello program build name Randy Dunlap
2008-10-09 23:52 ` [PATCH 2/8] docs: fix CDROM missing test program reference Randy Dunlap

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=12235963552413@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    /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