From: cgd@broadcom.com
To: ac131313@cygnus.com
Cc: gdb@sources.redhat.com
Subject: Re: http://sources.redhat.com/gdb/
Date: Tue, 21 Aug 2001 18:12:00 -0000 [thread overview]
Message-ID: <yov5vgjgrj77.fsf@highland.sibyte.com> (raw)
In-Reply-To: <mailpost.998402142.21082@postal.sibyte.com>
ac131313@cygnus.com ("Andrew Cagney") writes:
> 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.
I don't know what the exact protocol is for announcing minor changes,
so i'll just note that I fixed the 'download' link in the 5.1
announcement. (it was pointing into the void.)
cgd
--
Index: index.html
===================================================================
RCS file: /cvs/gdb/htdocs/index.html,v
retrieving revision 1.102
diff -c -r1.102 index.html
*** index.html 2001/08/20 03:24:33 1.102
--- index.html 2001/08/22 01:10:17
***************
*** 83,89 ****
<dd> The branch tag is <tt>gdb_5_1-2001-07-29-branch</tt>.<br>
Snapshots of the branch are available for <a
! href="/download">download</a> from the snapshots directory.<br>
Alternativly, the branch can be checked out using the CVS command:
<pre>
--- 83,89 ----
<dd> The branch tag is <tt>gdb_5_1-2001-07-29-branch</tt>.<br>
Snapshots of the branch are available for <a
! href="download">download</a> from the snapshots directory.<br>
Alternativly, the branch can be checked out using the CVS command:
<pre>
prev parent reply other threads:[~2001-08-21 18:12 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 ` http://sources.redhat.com/gdb/ Andrew Cagney
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 ` cgd [this message]
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=yov5vgjgrj77.fsf@highland.sibyte.com \
--to=cgd@broadcom.com \
--cc=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