From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Mark Wielaard <mark@klomp.org>,
Joel Brobecker <brobecker@adacore.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
gdb@sourceware.org, "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>,
Pedro Alves <pedro@palves.net>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: broken current onlinedocs
Date: Mon, 16 Jan 2023 07:42:32 +0400 [thread overview]
Message-ID: <Y8THqIQRupI+J/Oc@adacore.com> (raw)
In-Reply-To: <Y7+WylfsLOxvBvpQ@vapier>
> hmm, i can't tell if this is a new thing, but the gdb doc links are broken.
> i'm guessing it's new as this link has been the same since 2009 ?
>
> https://sourceware.org/gdb/documentation/
> -> Online GDB manuals: GDB User Manual
> https://sourceware.org/gdb/current/onlinedocs/gdb/
> -> 404
>
> but https://sourceware.org/gdb/current/onlinedocs/ seems to be correct.
I took a look, and this should be fixed, now.
--
Joel
next prev parent reply other threads:[~2023-01-16 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YZeHYvzZd+NTp+yy@vapier>
[not found] ` <6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net>
[not found] ` <YZpQsaSI9EyvwoLs@adacore.com>
[not found] ` <ca4fd206bd854a3613bd54a7af4c4ad6534534b2.camel@klomp.org>
[not found] ` <YZ4e/i9H0BELlV0r@vapier>
[not found] ` <Y1a6/JlhRSgfVEx2@vapier>
[not found] ` <Y1ckAXF+qMU2qM7J@elastic.org>
[not found] ` <f0ce6ccc94b6255f7eaec29d39001a9a2a7f0968.camel@klomp.org>
[not found] ` <Y7U2SBTabZ1AjFo2@vapier>
[not found] ` <20230105223840.GI8237@gnu.wildebeest.org>
2023-01-05 22:43 ` setting up sim project web space Mark Wielaard
2023-01-06 6:22 ` Joel Brobecker
2023-01-10 18:27 ` Frank Ch. Eigler
2023-01-10 20:18 ` Mark Wielaard
2023-01-11 5:36 ` Joel Brobecker
2023-01-11 23:56 ` Mark Wielaard
2023-01-12 5:12 ` broken current onlinedocs Mike Frysinger
2023-01-12 7:30 ` Mark Wielaard
2023-01-16 3:42 ` Joel Brobecker [this message]
2023-01-15 22:00 ` setting up sim project web space Mike Frysinger
2023-01-16 3:17 ` Joel Brobecker
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=Y8THqIQRupI+J/Oc@adacore.com \
--to=brobecker@adacore.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
--cc=vapier@gentoo.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).