public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dewar@gnat.com
To: dewar@gnat.com, guerby@acm.org
Cc: bosch@gnat.com, gcc@gcc.gnu.org
Subject: Re: [Ada] User Guide?
Date: Sun, 02 Dec 2001 09:53:00 -0000	[thread overview]
Message-ID: <20011202175242.B2EACF28C1@nile.gnat.com> (raw)

<<My question was: is this impractical on purely commercial grounds, ie
providing support to VMS people who do not want to hear about
UNIX, so the manual must either all VMS-ish or otherwise. Or is this
technically, texinfo-technology-wise impractical? If the latter, what
are the known technical problems?
>>

The point here is that unless we can meet the requirements of VMS users
in a single document, then we will be commited to having ACT maintain a
compeltely separate manual, which would force a compelte split here, and
we want to avoid that. There is no way that the gnu version of the manual
would stay up to date if that were to happen, and seeing as we think that
there are no insuperable technical problems, let's try that approach and
see if it works for everyone.

             reply	other threads:[~2001-12-02 17:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02  9:53 dewar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-02  9:51 dewar
2001-12-02  7:51 dewar
2001-12-02  7:47 dewar
2001-12-02  7:46 dewar
2001-12-02  7:41 dewar
2001-12-02  7:40 dewar
2001-12-02  9:01 ` guerby
2001-12-01  3:41 guerby
2001-12-01 19:52 ` Geert Bosch
2001-12-02  3:57   ` guerby
2001-12-02  4:43   ` Joseph S. Myers
2001-12-02  7:07     ` Florian Weimer

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=20011202175242.B2EACF28C1@nile.gnat.com \
    --to=dewar@gnat.com \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.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).