public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Updating the on-line documentation
Date: Sun, 22 Feb 2009 21:23:00 -0000	[thread overview]
Message-ID: <49A1C252.20805@eCosCentric.com> (raw)
In-Reply-To: <49A1A641.2060003@dallaway.org.uk>

John Dallaway wrote:
> 
> Updating the on-line docs could wait until the 3.0 final release, but I
> was thinking people would be more likely to be trawling over the docs
> during the beta period. I may take a look at updating them if I get a
> spare moment...

I knew it wouldn't take me long, so I've done it. For future ref, these 
are roughly the sort-of commands which make things a lot easier 
(substitute docsbuild where appropriate e.g. ~/ecos/trunk/doc/sgml/):

cd ecos/trunk/htdocs/docs-latest/something
rm *.html *.png
cp /docsbuild/*.html .
cp /docsbuild/*.png .
cvs -qn up | egrep ^\\? | awk '{print $2}' | xargs cvs add
cvs -qn up | egrep ^U | awk '{print $2}' | xargs cvs rm
cvs ci -m "Update docs to latest CVS"

Repeat for redboot, user-guide, cdl-guide.

Jifl
-- 
*See us at Embedded World 2009, Nürnberg, Germany, 3-5 Mar, Stand 11-300*
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

      reply	other threads:[~2009-02-22 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22  9:30 John Dallaway
2009-02-22 10:22 ` Andrew Lunn
2009-02-22 18:27   ` Jonathan Larmour
2009-02-22 19:23     ` John Dallaway
2009-02-22 21:23       ` Jonathan Larmour [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=49A1C252.20805@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).