ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-01-19 03:06:33 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix small issues in formatting

Browse Source 
* fix warning from "rst2html --verbose" by not using the in-line hyperlink
  syntax. The warning said::

    known_issues.rst:261: (INFO/1) Hyperlink target "google chart api" is not referenced.

* remove dead code (no-longer-referenced link), thus fixing another warning

* change links to relative files to be just $FILENAME instead of
  file:$FILENAME, which I think will fix the problem of broken links on the
  trac and github, e.g. the link in
  https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/known_issues.rst ,
  which ought to go to
  https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/cautions.rst , but
  instead goes to file:///cautions.rst
This commit is contained in:
Zooko Wilcox-O'Hearn 2013-10-05 03:29:00 +00:00
parent a0f477618d
commit 4e0a8d8d4f
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/known_issues.rst
View File

@ -1,7 +1,7 @@

See also cautions.rst_.
See also `cautions.rst`_.
.. _cautions.rst: file:cautions.rst
.. _cautions.rst: cautions.rst
============
Known Issues
@ -264,9 +264,11 @@ Operations" link on the front welcome page, then through the "Status" column
for "map-update" operations (which occur when mutable files, including
directories, are read or written). This page contains per-server response
times, as lines of text, and includes an image which displays the response
times in graphical form. The image is generated by constructing a URL for the
`Google Chart API <https://developers.google.com/chart/image/>`_, which is
then served by the `chart.apis.google.com` internet server.
times in graphical form. The image is generated by constructing a URL for
the `Google Chart API`_, which is then served by the `chart.apis.google.com`
internet server.
.. _Google Chart API: https://developers.google.com/chart/image/
When you view this page, several parties may learn information about your
Tahoe activities. The request will typically include a "Referer" header,
@ -336,9 +338,6 @@ There are three options:
could write the corrupted data back into place, making the damage
persistent)
.. _#1654: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654
----
Known Issues in Tahoe-LAFS v1.8.2, released 30-Jan-2011