public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
	gcc-patches@gcc.gnu.org,        java-patches@gcc.gnu.org
Subject: Re: [Java,wwwdocs] java/news.html -- remove broken link
Date: Tue, 23 Aug 2016 18:23:00 -0000	[thread overview]
Message-ID: <1471976596.8216.38.camel@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1608231337070.14886@anthias.pfeifer.com>

On Tue, 2016-08-23 at 13:43 +0200, Gerald Pfeifer wrote:
> I could not find a replacement link, and in any case, isn't the plan
> still to remove the Java frontend before the GCC 7 release?
> 
> Applied.
> 

FWIW I found the article inside a PDF at:
  https://www.redhat.com/en/files/resources/rh-magazine-issue-12.pdf
(pages 20-22)

> Gerald
> 
> 2016-08-23  Gerald Pfeifer  <gerald@pfeifer.com>
> 
> 	* news.html: Remove broken reference to online journal article.
> 
> Index: java/news.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/java/news.html,v
> retrieving revision 1.20
> diff -u -r1.20 news.html
> --- java/news.html	28 May 2016 13:08:43 -0000	1.20
> +++ java/news.html	23 Aug 2016 11:37:11 -0000
> @@ -26,8 +26,7 @@
>  
>  <dt>October 12, 2005</dt>
>  <dd>The October 2005 issue of Red Hat Magazine contains the article
> -&quot;<a href="
> https://www.redhat.com/magazine/012oct05/features/java/">The
> -state of Java on Linux</a>&quot; by Tom Tromey.</dd>
> +&quot;The State of Java on Linux&quot; by Tom Tromey.</dd>
>   <dt>September 23, 2005</dt>
>  <dd>Tom Tromey has imported <a

  reply	other threads:[~2016-08-23 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 11:43 Gerald Pfeifer
2016-08-23 18:23 ` David Malcolm [this message]
2016-08-23 23:08 ` Eric Gallager

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=1471976596.8216.38.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=java-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).