From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: http://sources.redhat.com/gdb/
Date: Tue, 21 Aug 2001 09:19:00 -0000 [thread overview]
Message-ID: <3B828253.7040700@cygnus.com> (raw)
In-Reply-To: <3B80A6EF.7040108@cygnus.com>
> FYI,
>
> I've finished overhalling it (ignoring a few cleanups). If you find a broken link or the like, just check out:
>
> cvs -d :ext:sources.redhat.com:/cvs/gdb htdocs
>
> and tweek.
Just FYI,
My current list of sugested cleanups:
o [download|cvs] or [download] [cvs] from ChrisF.
Ok with me. Any one got a preference?
Should there be separate gdb/download and
gdb/cvs directories? Probably not. Hmm, then again
it would allow a better separation of CVS(1)
and official FTP.
o all the old stray assignment forms
(Kevin, JimB will have the answer to
your question but he is busy right now.
It should be on the pages somewhere)
o rationalize the directories: documentation,
onlinedocs, papers and talks.
o find out if someone has tried exploder
along with other browsers (and a few WWW
checkers) on it. I've tried mozilla,
netscape and lynx.
o simplify further the update process,
a Makefile or something in CVS, er
mumble muble, security risk, mumble,
o re-audit and again try to reduce
the number of ``Red Hat''s :-)
Andrew
(1) I can see the day when ``cvs'' will be a link to the ``subversion''
repository ... :-)
next prev parent reply other threads:[~2001-08-21 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 6:52 http://sources.redhat.com/gdb/ Andrew Cagney
2001-08-21 9:19 ` Andrew Cagney [this message]
2001-08-22 9:42 ` http://sources.redhat.com/gdb/ Andrew Cagney
[not found] ` <mailpost.998402142.21082@postal.sibyte.com>
2001-08-21 18:12 ` http://sources.redhat.com/gdb/ cgd
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=3B828253.7040700@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.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