Devicetree
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Yoder Stuart-B08248 <B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: devicetree-discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: Re: new device tree binding review process idea
Date: Thu, 8 Apr 2010 10:16:41 -0600	[thread overview]
Message-ID: <l2ufa686aa41004080916jcb4e6dddzad4bc19306d32baa@mail.gmail.com> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA305CAFFD0-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>

On Thu, Apr 8, 2010 at 9:04 AM, Yoder Stuart-B08248
<B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:
>> Mediawiki is as readable as any, and it's got the advantage of a
>> stable and well supported application behind it.  I've used mediawiki
>> for a while now, and it's pretty much proven that it scales well, and
>> does a good job of handling off-line edits.  Although I would agree
>> that it makes sense to define a binding template and formating guide
>> to keep things looking uniform and readable.
>
> Ok.  I do think that the wiki formatting will keep things a bit more
> readable via web browsers, which will be the primary way people
> are reading this.
>
> I do have a few ideas/suggestions for a binding template that I
> will post for comments soon.

Excellent!  Thanks.  I'll watch out for them.

g.

      parent reply	other threads:[~2010-04-08 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26  5:13 RFC: new device tree binding review process idea Grant Likely
     [not found] ` <fa686aa41003252213w3f403d42pea3c8c88adbf5832-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-06 15:04   ` Yoder Stuart-B08248
     [not found]     ` <9696D7A991D0824DBA8DFAC74A9C5FA305CAFB62-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2010-04-06 19:48       ` Grant Likely
     [not found]         ` <m2nfa686aa41004061248w8e5fad71sb7d1871c80787d9c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-08 15:04           ` Yoder Stuart-B08248
     [not found]             ` <9696D7A991D0824DBA8DFAC74A9C5FA305CAFFD0-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2010-04-08 16:16               ` Grant Likely [this message]

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=l2ufa686aa41004080916jcb4e6dddzad4bc19306d32baa@mail.gmail.com \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.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