public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Fred Wheeler <wheeler@cipr.rpi.edu>
Cc: egcs@egcs.cygnus.com, egcs-patches@egcs.cygnus.com
Subject: Re: Addition to EGCS FAQ Octave entry
Date: Sun, 21 Mar 1999 09:47:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.10.9903211844120.1651-100000@markab.dbai.tuwien.ac.at> (raw)
In-Reply-To: < 14065.21599.705039.901113@cipr.no_spam.rpi.edu >

On Thu, 18 Mar 1999, Fred Wheeler wrote:
> So, you might want to add this to the FAQ:
> 
>   Octave 2.0.13.96, a test release, has been compiled without patches by 
>   egcs 1.1.2.  It is available at
>   ftp://ftp.che.wisc.edu/pub/octave/test-releases/

Thanks for the hint; I have applied the patch below to our FAQ.

Gerald

Index: faq.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/faq.html,v
retrieving revision 1.114
diff -r1.114 faq.html
856c856,862
< to Octave</a> should fix this.
---
> to Octave</a> should fix this.</p>
> 
> <p>Octave 2.0.13.96, a test release, has been compiled without patches by
> egcs 1.1.2.  It is available at
> <a href=" ftp://ftp.che.wisc.edu/pub/octave/test-releases/ ">
> ftp://ftp.che.wisc.edu/pub/octave/test-releases/ </a>.</p>
> 
1114c1120
< <p><i>Last modified:  March 10, 1999</i>
---
> <p><i>Last modified:  March 21, 1999</i>

WARNING: multiple messages have this Message-ID

From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Fred Wheeler <wheeler@cipr.rpi.edu>
Cc: egcs@egcs.cygnus.com, egcs-patches@egcs.cygnus.com
Subject: Re: Addition to EGCS FAQ Octave entry
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.10.9903211844120.1651-100000@markab.dbai.tuwien.ac.at> (raw)
Message-ID: <19990331234600.tPN6zmsoE_D8bpQ2qfJ7__0No6d-BXtLx7VhF5O9ucw@z> (raw)
In-Reply-To: <14065.21599.705039.901113@cipr.no_spam.rpi.edu>

On Thu, 18 Mar 1999, Fred Wheeler wrote:
> So, you might want to add this to the FAQ:
> 
>   Octave 2.0.13.96, a test release, has been compiled without patches by 
>   egcs 1.1.2.  It is available at
>   ftp://ftp.che.wisc.edu/pub/octave/test-releases/

Thanks for the hint; I have applied the patch below to our FAQ.

Gerald

Index: faq.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/faq.html,v
retrieving revision 1.114
diff -r1.114 faq.html
856c856,862
< to Octave</a> should fix this.
---
> to Octave</a> should fix this.</p>
> 
> <p>Octave 2.0.13.96, a test release, has been compiled without patches by
> egcs 1.1.2.  It is available at
> <a href=" ftp://ftp.che.wisc.edu/pub/octave/test-releases/ ">
> ftp://ftp.che.wisc.edu/pub/octave/test-releases/ </a>.</p>
> 
1114c1120
< <p><i>Last modified:  March 10, 1999</i>
---
> <p><i>Last modified:  March 21, 1999</i>


  parent reply	other threads:[~1999-03-21  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-18 11:30 Fred Wheeler
     [not found] ` < 14065.21599.705039.901113@cipr.no_spam.rpi.edu >
1999-03-21  9:47   ` Gerald Pfeifer [this message]
1999-03-31 23:46     ` Gerald Pfeifer
1999-03-31 23:46 ` Fred Wheeler

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=Pine.GSO.4.10.9903211844120.1651-100000@markab.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=egcs-patches@egcs.cygnus.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=wheeler@cipr.rpi.edu \
    /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).