public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Christophe Coutand <ccoutand@stmi.com>
Cc: eCos Patches <ecos-patches@ecos.sourceware.org>
Subject: RE: AT91 ADC support
Date: Sun, 30 May 2010 13:46:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1005301637170.5258@sg-laptop> (raw)
In-Reply-To: <D6050C555CC56940A7AF32652283027602EACA92@mail2.STMIRV01.COM>

On Sun, 30 May 2010, Christophe Coutand wrote:
> Hi Sergei,
>
> Thanks. Additionally, can you clarify something for me. When updating
> the eCos documentation, are the SGML files part of the source code
> repository used to generate the HTML version of the documentation? Or
> should both be updated separately?

Hi Christophe,

You will need to create a per-package `docs' directory, write own doc
entry in SGML Then it's needed to update ecos/doc/sgml/doclist to point
on new entry.

Sergei

  reply	other threads:[~2010-05-30 13:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22  9:40 Christophe Coutand
2010-05-27 13:42 ` John Dallaway
2010-05-27 13:52   ` Sergei Gavrikov
2010-05-27 14:16     ` Christophe Coutand
2010-05-27 14:47       ` John Dallaway
2010-05-27 15:44         ` Christophe Coutand
2010-05-27 16:08           ` John Dallaway
2010-05-27 16:37             ` Kurt Siedenburg
2010-05-27 16:37           ` Sergei Gavrikov
2010-05-27 19:49             ` Christophe Coutand
2010-05-27 21:44               ` Sergei Gavrikov
2010-05-29 10:24                 ` Sergei Gavrikov
2010-05-29 13:10                   ` John Dallaway
2010-05-30 10:34                     ` Sergei Gavrikov
2010-05-30 12:40                       ` Christophe Coutand
2010-05-30 13:46                         ` Sergei Gavrikov [this message]
2011-02-22 11:33                   ` John Dallaway
2010-05-27 21:37             ` Christophe Coutand

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=alpine.DEB.2.00.1005301637170.5258@sg-laptop \
    --to=sergei.gavrikov@gmail.com \
    --cc=ccoutand@stmi.com \
    --cc=ecos-patches@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).