From a2cf8d6d317716cf2d7451b799855f11f6349b51 Mon Sep 17 00:00:00 2001 From: Johnny Willemsen Date: Wed, 23 Jan 2019 19:55:20 +0100 Subject: Fixed several broken links and updated bugzilla to github --- ACE/ACE-INSTALL.html | 14 +++++++------- ACE/docs/ACE-bug-process.html | 12 ++++++------ 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/ACE/ACE-INSTALL.html b/ACE/ACE-INSTALL.html index 844d53d5d38..8e526bdc2b7 100644 --- a/ACE/ACE-INSTALL.html +++ b/ACE/ACE-INSTALL.html @@ -38,22 +38,22 @@ pre, code { The file explains how to build and install ACE, its Network Services, test suite and examples on the various OS platforms and compilers that it has been ported to. Please consult the NEWS and -ChangeLog files to see whether any recent changes +ChangeLogs files to see whether any recent changes to the release will affect your code. In addition, you should check out our development process. As you start working with ACE, we suggest you get copies of the C++NPv1, C++NPv2, and +href="http://www.dre.vanderbilt.edu/~schmidt/ACE/book1/">C++NPv1, C++NPv2, and APG books to help guide you after you've built and installed ACE. You should also consult the ACE Frequently Made Mistakes page. If you encounter any problems or -would like to request an enhancement, then use our bug -tracking system to submit a report in accordance with our github + to submit an issue in accordance with our bug report process.

@@ -189,7 +189,7 @@ document.

The Intel C++ compiler is supported on Windows 32/64bit, Linux IA32/EM64T/IA64, MacOSX. - Remedy IT web site and + Remedy IT web site and the TAO install document diff --git a/ACE/docs/ACE-bug-process.html b/ACE/docs/ACE-bug-process.html index 85ee8abbf29..895946cbc14 100644 --- a/ACE/docs/ACE-bug-process.html +++ b/ACE/docs/ACE-bug-process.html @@ -74,9 +74,9 @@ our sponsors we'll try to fix it as time permits.

-

  • You should also consider entering your bug report into our bug tracking -database so that it's archived for future processing. As usual, +
  • You should also consider entering your bug report into a github issue +so that it's archived for future processing. As usual, we try to address these bugs as time permits, but may not get to them for a while unless it affects our work or the work of our sponsors.

    @@ -87,7 +87,7 @@ HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-mail.html">ACE users (ace-users@list.isis.vanderbilt.edu), TAO users (tao-users@list.isis.vanderbilt.edu), -and CIAO +and CIAO users (ciao-users@list.isis.vanderbilt.edu) mailing lists, where the open-source user community may already have @@ -162,9 +162,9 @@ with our software here's the process for submitting it: will end up in the ATCD ChangeLog. When you have tested your changes at least on Windows and Linux prepare a pull request.

    -

  • Create a ``unified diff'' of all changes and put this into Bugzilla at

    +

  • Create a ``unified diff'' of all changes and put this into a github issue at

    - http://bugzilla.dre.vanderbilt.edu/

    + https://github.com/DOCGroup/ACE_TAO

    and send an email to the appropriate mailing -- cgit v1.2.1