From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: overseers@gcc.gnu.org
Subject: [Bug web/2036] More broken gcc-cvs links
Date: Mon, 26 Nov 2007 13:49:00 -0000 [thread overview]
Message-ID: <20071126134906.12047.qmail@sourceware.org> (raw)
In-Reply-To: <bug-2036-230@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from steven at gcc dot gnu dot org 2007-11-26 13:49 -------
The entire repo has been converted to SVN. This obviously doesn't fix the
almost 7 year old broken links, but is it enough reason to close this bug
report at least?
--
steven at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2036
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-11-26 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-2036-230@http.gcc.gnu.org/bugzilla/>
2005-12-10 5:30 ` pinskia at gcc dot gnu dot org
2007-11-26 13:49 ` steven at gcc dot gnu dot org [this message]
2008-01-02 8:34 ` gerald at pfeifer dot com
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=20071126134906.12047.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=overseers@gcc.gnu.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).