mirror of
https://github.com/boostorg/website.git
synced 2026-01-19 04:42:17 +00:00
167 lines
6.5 KiB
HTML
167 lines
6.5 KiB
HTML
<!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=utf-8" />
|
|
<link rel="icon" href="/favicon.ico" type="image/ico" />
|
|
<link rel="stylesheet" type="text/css" href=
|
|
"/style-v2/section-development.css" />
|
|
<!--[if IE 7]> <style type="text/css"> body { behavior: url(/style-v2/csshover3.htc); } </style> <![endif]-->
|
|
<script defer data-domain="original.boost.org" src="https://plausible.io/js/script.js"></script></head><!--
|
|
Note: Editing website content is documented at:
|
|
https://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=
|
|
"https://github.com/boostorg/wiki/wiki/Getting-Started" class=
|
|
"external">git repositories</a>.</li>
|
|
|
|
<li><a href="https://github.com/boostorg/">Search the issues</a>
|
|
on GitHub 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>
|
|
<p><a href="https://github.com/boostorg/">Create a new issues</a>
|
|
in the repository of the particular library of your interest.</p>
|
|
|
|
<p>If possible,</p>
|
|
|
|
<ul>
|
|
<li>Describe the problem carefully, including steps required to
|
|
reproduce it by a library maintainers.</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>
|
|
<p>After completing the steps above, please submit a patch
|
|
or a pull request as described in
|
|
<a href="https://svn.boost.org/trac/boost/wiki/StartModPatchAndPullReq"
|
|
title="Getting Started with Patches and Pull Requests">the wiki</a>.</p>
|
|
</div>
|
|
|
|
<!-- The old subversion instructions:
|
|
|
|
<div>
|
|
<p>After completing the steps above,</p>
|
|
|
|
<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-development.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>
|