From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: gleb@minantech.com, mingo@elte.hu, akpm@osdl.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 00/02] update to Document futex PI design
Date: Sat, 13 May 2006 10:15:45 -0700 [thread overview]
Message-ID: <20060513101545.8afeb220.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0605131303100.27751@gandalf.stny.rr.com>
On Sat, 13 May 2006 13:07:46 -0400 (EDT) Steven Rostedt wrote:
>
> On Sat, 13 May 2006, Randy.Dunlap wrote:
>
> > On Wed, 10 May 2006 09:27:48 -0400 (EDT) Steven Rostedt wrote:
> >
> > >
> > > Andrew,
> > >
> > > The following two patches update the rt-mutex-design.txt document.
> > >
> > > The first one simply removes all the tabs that I had in that document.
> > > Since it's a document and not code, tabs are not really appropiate.
> >
> > I think that lots of people would not agree with that sentiment.
> > Documentation/*.txt has approximately 8800 lines with tabs in them
> > (just top-level Doc/*.txt, not sub-directories).
>
> Yeah, but I have few ascii art graphs, as well as notes and points, that
> would look funny if you don't have 8 character tabs.
OK, spaces do make sense for that IMO.
But tabs are perfectly fine in text indentations.
> But If the standand is to have tabs, then I would convert all 8
> consecutive spaces to use tabs. But the original document had a mix of
> tabs and spaces that just looked horrible on different editors. So I
> decided to use spaces since that is more consistent, in the look.
Sure, mixing is often ugly/bad.
> But if this is not the norm, I'll supply a patch, otherwise I'll let it
> be.
Who can answer that?
---
~Randy
next prev parent reply other threads:[~2006-05-13 17:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 13:55 [PATCH] " Steven Rostedt
2006-05-10 7:37 ` Steven Rostedt
2006-05-10 8:33 ` Steven Rostedt
2006-05-10 10:17 ` Ingo Molnar
2006-05-10 10:59 ` Steven Rostedt
2006-05-10 12:46 ` Gleb Natapov
2006-05-10 13:09 ` Steven Rostedt
2006-05-10 13:27 ` [PATCH -mm 00/02] update to " Steven Rostedt
2006-05-10 13:30 ` [PATCH -mm 01/02] Remove tabs from " Steven Rostedt
2006-05-10 13:36 ` [PATCH -mm 02/02] Redefine "lock" in " Steven Rostedt
2006-05-13 17:01 ` [PATCH -mm 00/02] update to " Randy.Dunlap
2006-05-13 17:07 ` Steven Rostedt
2006-05-13 17:15 ` Randy.Dunlap [this message]
2006-05-14 3:14 ` [PATCH] " Randy.Dunlap
2006-05-14 14:00 ` Steven Rostedt
2006-05-14 18:28 ` Randy.Dunlap
2006-05-15 6:25 ` Steven Rostedt
2006-05-15 7:21 ` Steven Rostedt
2006-05-15 9:09 ` Steven Rostedt
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=20060513101545.8afeb220.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=gleb@minantech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®