Devicetree
 help / color / mirror / Atom feed
From: Nate Case <ncase-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
To: Matt Sealey <matt-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
Cc: Benjamin Herrenschmidt
	<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>,
	Anton Vorontsov
	<avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>,
	devicetree-discuss list
	<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
	Hugh Blemings <hab-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.org>
Subject: Re: Device tree binding documentation
Date: Tue, 28 Oct 2008 15:54:10 -0500	[thread overview]
Message-ID: <1225227250.30047.151.camel@localhost.localdomain> (raw)
In-Reply-To: <49076A8C.3010105-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>

On Tue, 2008-10-28 at 14:39 -0500, Matt Sealey wrote:
> I guess we would need to decide how those documents are published
> without using proprietary software, then, and easily committed to
> another git repository (or the same one just in a published form).
> I don't suppose office xml is a good choice? It should be flexible
> enough and similar enough that sections and layout do not change a
> great deal, and git can easily produce diffs?

I would suggest using DocBook if publishing PDFs is a goal.  It would
also let you output text and HTML as an added bonus.

-- 
Nate Case <ncase-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>

  parent reply	other threads:[~2008-10-28 20:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28  6:23 Device tree binding documentation Grant Likely
     [not found] ` <fa686aa40810272323s4a5c2f50u8aa999952aaa6b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-28 16:07   ` Yoder Stuart
     [not found]     ` <9696D7A991D0824DBA8DFAC74A9C5FA3047E572F-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2008-10-28 16:58       ` Matt Sealey
     [not found]         ` <490744B1.2000602-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
2008-10-28 17:02           ` Scott Wood
     [not found]             ` <49074593.1040008-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-10-28 17:25               ` Matt Sealey
     [not found]                 ` <49074AFF.3080106-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
2008-10-28 18:18                   ` Mitch Bradley
2008-10-28 17:27           ` Grant Likely
     [not found]             ` <fa686aa40810281027r64d4f78enfcb1c92c9ac6401e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-28 19:39               ` Matt Sealey
     [not found]                 ` <49076A8C.3010105-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
2008-10-28 20:54                   ` Nate Case [this message]
     [not found]                     ` <1225227250.30047.151.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-10-29 14:53                       ` Matt Sealey
     [not found]                         ` <490878D5.2010607-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
2008-11-17 17:37                           ` Jon Loeliger
2008-11-17 18:47                             ` Jimi Xenidis
2008-11-17 19:09                             ` Matt Sealey
2008-11-18  0:51                             ` David Gibson

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=1225227250.30047.151.camel@localhost.localdomain \
    --to=ncase-aqeff1f/brxbdgjk7y7tuq@public.gmane.org \
    --cc=avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org \
    --cc=benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=hab-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.org \
    --cc=matt-sEEEE4iEDtaXzmuOJsdVMQ@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