From: Jason Molenda <jason-swarelist@molenda.com>
To: Jeffrey A Law <law@cygnus.com>
Cc: Benjamin Kosnik <bkoz@cygnus.com>,
overseers@sourceware.cygnus.com, mark@codesourcery.com
Subject: Re: libstdc++-v3 module moved into egcs
Date: Mon, 24 Apr 2000 10:32:00 -0000 [thread overview]
Message-ID: <20000424103205.B12921@shell17.ba.best.com> (raw)
Message-ID: <20000424103200.Cn4nUcjUhXoELFw2_00TTl7ttAq7_4z2U7wDyRvGRzY@z> (raw)
In-Reply-To: <6319.956591987@upchuck>
On Mon, Apr 24, 2000 at 09:59:47AM -0600, Jeffrey A Law wrote:
> > 4) The documentation in the CVS repository is the basis for the
> > libstdc++-v3 on-line documentation. This needs to be moved over to
> > point to the egcs/libstdc++-v3/docs directory instead of what's
> > currently in place.
> I'm not sure I 100% follow.
Benjamin has the web pages right in the source directory; it allows
him to publish distributions with all of the documentation included.
Whatever. It's different than what other packages do, but I don't
see it as particularly better or worse.
The important point is that he has a (ever so slightly) customized
script which does the check-out/updating of these pages in the web
server's htdocs dir. It just needs to be tweaked a little to
recognize the new repo location and to throw its files into
/www/gcc/htdocs/libstdc++ or something instead of the old location.
J
next prev parent reply other threads:[~2000-04-24 10:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Benjamin Kosnik
2000-04-21 15:11 ` Benjamin Kosnik
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 17:42 ` Mark Mitchell
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:08 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-04-24 10:11 ` Tom Tromey
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:31 ` Jeffrey A Law
2000-12-30 6:08 ` Gerald Pfeifer
2000-04-26 14:56 ` Gerald Pfeifer
2000-12-30 6:08 ` Tom Tromey
2000-04-26 15:00 ` Tom Tromey
2000-12-30 6:08 ` Jason Molenda [this message]
2000-04-24 10:32 ` Jason Molenda
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:58 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-04-21 17:13 ` Tom Tromey
2000-12-30 6:08 ` Jason Molenda
2000-04-21 17:35 ` Jason Molenda
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 17:47 ` Mark Mitchell
2000-12-30 6:08 ` Jason Molenda
2000-04-21 18:04 ` Jason Molenda
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 23:13 ` Mark Mitchell
2000-12-30 6:08 ` Andrew Cagney
2000-04-21 23:29 ` Andrew Cagney
[not found] <39014BB3.B681D244@nabi.net>
2000-12-30 6:08 ` Benjamin Kosnik
2000-04-21 23:56 ` Benjamin Kosnik
2000-12-30 6:08 Benjamin Kosnik
2000-04-24 11:22 ` Benjamin Kosnik
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=20000424103205.B12921@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=bkoz@cygnus.com \
--cc=law@cygnus.com \
--cc=mark@codesourcery.com \
--cc=overseers@sourceware.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).