Subject: [Boost-commit] svn:boost r84365 - in website/public_html/live: common development support users
From: dnljms_at_[hidden]
Date: 2013-05-19 01:42:44
Author: danieljames
Date: 2013-05-19 01:42:43 EDT (Sun, 19 May 2013)
New Revision: 84365
URL: http://svn.boost.org/trac/boost/changeset/84365
Log:
Move bugs.html into development section.
Added:
website/public_html/live/development/bugs.html (contents, props changed)
- copied, changed from r84364, /website/public_html/live/support/bugs.html
website/public_html/live/support/.htaccess (contents, props changed)
Removed:
website/public_html/live/support/bugs.html
Text files modified:
website/public_html/live/common/menu-development.html | 2 +-
website/public_html/live/common/menu-welcome.html | 2 +-
website/public_html/live/development/bugs.html | 5 ++---
website/public_html/live/users/faq.html | 2 +-
4 files changed, 5 insertions(+), 6 deletions(-)
Modified: website/public_html/live/common/menu-development.html
==============================================================================
--- website/public_html/live/common/menu-development.html (original)
+++ website/public_html/live/common/menu-development.html 2013-05-19 01:42:43 EDT (Sun, 19 May 2013)
@@ -7,7 +7,7 @@
"link">></span></a>
</li>
- <li><a href="/support/bugs.html" class="internal">Reporting and Fixing
+ <li><a href="/development/bugs.html" class="internal">Reporting and Fixing
Bugs<span class="link">></span></a></li>
<li>
Modified: website/public_html/live/common/menu-welcome.html
==============================================================================
--- website/public_html/live/common/menu-welcome.html (original)
+++ website/public_html/live/common/menu-welcome.html 2013-05-19 01:42:43 EDT (Sun, 19 May 2013)
@@ -13,7 +13,7 @@
<li><a href="/community/groups.html">Mailing Lists <span class=
"link">></span></a></li>
- <li><a href="/support/bugs.html" class="internal">Reporting and Fixing
+ <li><a href="/development/bugs.html" class="internal">Reporting and Fixing
Bugs<span class="link">></span></a></li>
<li><a href="https://svn.boost.org/trac/boost/" class="external">Wiki<span class=
Copied: website/public_html/live/development/bugs.html (from r84364, /website/public_html/live/support/bugs.html)
==============================================================================
--- /website/public_html/live/support/bugs.html (original)
+++ website/public_html/live/development/bugs.html 2013-05-19 01:42:43 EDT (Sun, 19 May 2013)
@@ -7,7 +7,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<link rel="icon" href="/favicon.ico" type="image/ico" />
<link rel="stylesheet" type="text/css" href=
- "../style-v2/section-support.css" />
+ "/style-v2/section-development.css" />
<!--[if IE 7]> <style type="text/css"> body { behavior: url(/style-v2/csshover3.htc); } </style> <![endif]-->
</head><!--
Note: Editing website content is documented at:
@@ -145,7 +145,7 @@
<div id="sidebar">
<!--#include virtual="/common/sidebar-common.html" -->
- <!--#include virtual="/common/sidebar-support.html" -->
+ <!--#include virtual="/common/sidebar-development.html" -->
</div>
<div class="clear"></div>
Added: website/public_html/live/support/.htaccess
==============================================================================
--- (empty file)
+++ website/public_html/live/support/.htaccess 2013-05-19 01:42:43 EDT (Sun, 19 May 2013)
@@ -0,0 +1,4 @@
+RewriteEngine On
+RewriteBase /support
+
+RewriteRule ^bugs.html http://www.boost.org/development/bugs.html [R=301]
Deleted: website/public_html/live/support/bugs.html
==============================================================================
--- website/public_html/live/support/bugs.html 2013-05-19 01:42:43 EDT (Sun, 19 May 2013)
+++ (empty file)
@@ -1,174 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
- <title>Bugs</title>
- <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
- <link rel="icon" href="/favicon.ico" type="image/ico" />
- <link rel="stylesheet" type="text/css" href=
- "../style-v2/section-support.css" />
- <!--[if IE 7]> <style type="text/css"> body { behavior: url(/style-v2/csshover3.htc); } </style> <![endif]-->
-</head><!--
-Note: Editing website content is documented at:
-http://www.boost.org/development/website_updating.html
--->
-
-<body>
- <div id="heading">
- <!--#include virtual="/common/heading.html" -->
- </div>
-
- <div id="body">
- <div id="body-inner">
- <div id="content">
- <div class="section" id="intro">
- <div class="section-0">
- <div class="section-title">
- <h1>Reporting Boost bugs</h1>
- </div>
-
- <div class="section-body">
- <div>
- <ol>
- <li>If you know where to look in the source code, make sure
- the bug isn't already fixed in the latest sources. The most
- recent version of everything on the Boost web site is
- available from the <a href=
- "http://svn.boost.org/trac/boost/wiki/BoostSubversion"
- class="external">boost public subversion
- repository</a>.</li>
-
- <li><a href=
- "http://svn.boost.org/trac/boost/search?ticket=on">Search
- the bug database</a> to make sure we don't already know
- about the bug. If we do, you can add further information to
- an existing bug ticket.</li>
-
- <li>If you have a userid on the Boost Trac server, please
- <a href="http://svn.boost.org/trac/boost/login">log
- in</a>.</li>
-
- <li><strong>Even if you don't have a userid</strong>, visit
- <a href="http://svn.boost.org/trac/boost/prefs">the
- preferences page</a> to enter or confirm an email address at
- which you can be reached. Most bug reports require some
- interaction with the reporter, and if we can't follow up
- with you, chances are good that your efforts at reporting
- the bug will be wasted.</li>
-
- <li>
- <p><a href=
- "http://svn.boost.org/trac/boost/newticket">Create a new
- ticket</a> in the bug tracker.</p>
-
- <p>If possible,</p>
-
- <ul>
- <li>Fill out all the fields completely, especially the
- “component” field that identifies the
- library. That will help ensure your report is noticed
- by the appropriate developers.</li>
-
- <li>Attach a <em>minimal</em> and <em>complete</em>
- program that reproduces the problem. Aside from helping
- the library maintainer fix the problem, you may find
- the bug in your own code, which can avoid a costly
- delay waiting for a response.</li>
- </ul>
- </li>
- </ol>
- </div>
-
- <h2>If You Have a Fix for the Bug</h2>
-
- <div>
- After completing the steps above,
-
- <ul>
- <li>
- <p>If you <em>are not</em> a boost developer, attach a
- patch for the code in the <em>unified diff</em> format,
- along with an explanation of your proposed fix. If you
- can, make a patch relative to the current subversion
- state.</p>
-
- <p>To create a patch file:</p>
-
- <ol>
- <li>Get the latest version of the files you're fixing
- <a href="http://svn.boost.org/svn/boost">directly from
- subversion</a>.</li>
-
- <li>Make sure that the bug is still present in the
- code.</li>
-
- <li>If you got your code directly from subversion, make
- your fixes, and then execute “<code>svn diff >
- <var>patchfile</var>.patch</code>” from a
- directory in your working copy that contains all your
- changes.</li>
-
- <li>Otherwise, make a full recursive copy of a
- directory containing the files in question, make your
- fixes in the new copy, then execute “<code>diff
- -dur <var>olddirectory</var> <var>newdirectory</var>
- > <var>patchfile</var>.patch</code>”</li>
- </ol>
- </li>
-
- <li>If you <em>are</em> a Boost developer,
-
- <ul>
- <li>If the bug is trivial (e.g. misspelled name, missed
- <code>typename</code>, etc.), you can assign the ticket
- to yourself and check the fix into subversion,
- inserting “fixes #<var>ticket number</var>”
- in the log comment to automatically close the ticket.
- However, please keep the library's maintainer in the
- loop by adding his Trac userid or email address to the
- ticket's Cc: field.</li>
-
- <li>Otherwise, create a temporary branch in subversion,
- make your changes there, and ask the library
- author(s)/maintainer(s) to review them; if approve the
- new code, either you or they can integrate the fixes
- into the main trunk.</li>
- </ul>
- </li>
- </ul>
- </div>
- </div>
- </div>
- </div>
- </div>
-
- <div id="sidebar">
- <!--#include virtual="/common/sidebar-common.html" -->
- <!--#include virtual="/common/sidebar-support.html" -->
- </div>
-
- <div class="clear"></div>
- </div>
- </div>
-
- <div id="footer">
- <div id="footer-left">
- <div id="revised">
- <p>Revised $Date$</p>
- </div>
-
- <div id="copyright">
- <p>Copyright <a href="/users/people/aleksey_gurtovoy.html">Aleksey
- Gurtovoy</a> 2002</p>
- </div><!--#include virtual="/common/footer-license.html" -->
- </div>
-
- <div id="footer-right">
- <!--#include virtual="/common/footer-banners.html" -->
- </div>
-
- <div class="clear"></div>
- </div>
-</body>
-</html>
Modified: website/public_html/live/users/faq.html
==============================================================================
--- website/public_html/live/users/faq.html (original)
+++ website/public_html/live/users/faq.html 2013-05-19 01:42:43 EDT (Sun, 19 May 2013)
@@ -249,7 +249,7 @@
<p class="faq"><span class="faq-question">What should I do if I
spot a bug in the Boost code or documentation?</span> See the
- suggestions on the <a href="/support/bugs.html">Bugs
+ suggestions on the <a href="/development/bugs.html">Bugs
page</a>.</p>
<p class="faq"><span class="faq-question">How can I request a