From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: law@cygnus.com
Cc: egcs@egcs.cygnus.com
Subject: Re: egcs-1.1.2 prerelease #2
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.9903190031590.9596-100000@alphard.dbai.tuwien.ac.at> (raw)
Message-ID: <19990331234600.gypYRkFV_4PhU8FFYmfaotCznV_ttp8SpobFWXjI_nk@z> (raw)
In-Reply-To: <9400.921563855@hurl.cygnus.com>
On Mon, 15 Mar 1999, Jeffrey A Law wrote:
>> In our wwwdocs repository and on the web the directory is called
>> "install", while when shipped with releases we call it "INSTALL".
> Maybe the better thing to do is rework the web pages so that they use
> "INSTALL" isntead of "install" -- I'd prefer to avoid unnecessary sed-ing
> for releases. The more closely those bits in the cvs tree match what we
> want to ship with releases, the better.
I agree that sed-ing should be avoided where possible.
> Objections?
Hmm, in general we don't use all-uppercase strings as part of URLs and
personally I prefer the lower-case versions as well, but neither is a real
reason not to go with "INSTALL".
However, note that we just have shipped egcs 1.1.2 with the following in
INSTALL/index.html:
<p>The latest version of this document is always available at <a href="
http://egcs.cygnus.com/install/ "> http://egcs.cygnus.com/install/ </a>.
So what do you think about the following?
We include the installation notes for the release as "install" and add a
short text file "INSTALL" explaining where to look for these installation
notes.
No sed-ing nor changes to wwwdocs will be needed and it will even be an
improvement, in that currently we do not provide any information about
_which_ of those files in "INSTALL" one should start with!
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-24 20:49 Jeffrey A Law
[not found] ` < 18344.919918142@hurl.cygnus.com >
1999-02-24 21:08 ` Shawn Leas
[not found] ` < 19990224230733.A7961@ixion.honeywell.com >
1999-02-25 1:06 ` Jeffrey A Law
1999-02-28 22:53 ` Jeffrey A Law
1999-02-28 22:53 ` Shawn Leas
1999-02-26 16:56 ` Gerald Pfeifer
1999-02-28 22:53 ` Gerald Pfeifer
1999-03-10 16:14 ` Gerald Pfeifer
[not found] ` < Pine.GSO.4.10.9903110111410.22761-100000@alphard.dbai.tuwien.ac.at >
1999-03-14 2:33 ` Jeffrey A Law
[not found] ` < 9981.921406931@upchuck >
1999-03-15 14:47 ` Gerald Pfeifer
[not found] ` < Pine.GSO.4.10.9903152337480.9819-100000@alphard.dbai.tuwien.ac.at >
1999-03-15 21:57 ` Jeffrey A Law
[not found] ` < 9400.921563855@hurl.cygnus.com >
1999-03-18 15:43 ` Gerald Pfeifer [this message]
[not found] ` < Pine.GSO.4.10.9903190031590.9596-100000@alphard.dbai.tuwien.ac.at >
1999-03-18 16:00 ` David Edelsohn
1999-03-31 23:46 ` David Edelsohn
1999-03-31 23:46 ` Gerald Pfeifer
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Gerald Pfeifer
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Gerald Pfeifer
1999-02-28 22:53 ` Jeffrey A Law
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=Pine.GSO.4.10.9903190031590.9596-100000@alphard.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=egcs@egcs.cygnus.com \
--cc=law@cygnus.com \
/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).