public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] fix URL
Date: Mon, 02 Mar 2015 20:37:00 -0000	[thread overview]
Message-ID: <54F4C9EB.10900@codesourcery.com> (raw)
In-Reply-To: <87y4nf45ya.fsf@gmail.com>

On 03/02/2015 11:20 AM, Ulrich Drepper wrote:
> A trivial patch to fix the URL of my paper referenced in the
> documentation.  The RH server isn't the canonical address even though it
> will automatically redirect to the correct address.  At least for now,
> who knows.
>
>
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index a87376e..6e7cc82 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -23644,7 +23644,7 @@ GCC@.
>   A good explanation of the benefits offered by ensuring ELF
>   symbols have the correct visibility is given by ``How To Write
>   Shared Libraries'' by Ulrich Drepper (which can be found at
> -@w{@uref{http://people.redhat.com/~drepper/}})---however a superior
> +@w{@uref{http://www.akkadia.org/drepper/}})---however a superior
>   solution made possible by this option to marking things hidden when
>   the default is public is to make the default hidden and mark things
>   public.  This is the norm with DLLs on Windows and with @option{-fvisibility=hidden}

I'd prefer to link directly to the cited paper if possible, but if the 
new URL is an exact replacement for the old one this is OK.

-Sandra

  reply	other threads:[~2015-03-02 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 18:20 Ulrich Drepper
2015-03-02 20:37 ` Sandra Loosemore [this message]
2015-03-04 21:14 ` Gerald Pfeifer

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=54F4C9EB.10900@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=drepper@gmail.com \
    --cc=gcc-patches@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).