revi-archive/phorge-phorge
1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-11-23 07:12:41 +01:00
Code Issues Releases Wiki Activity

Unindent various links

Browse source 
Summary: @btrahan asked about this but I gave the wrong answer. These
currently do not turn into links. I think they might have in the past,
but if they did the rule is a little weird and feels specific to my
use. We can reexamine this at some point, but for now just make the
links work in a normal, reasonable sort of way.

Auditors: btrahan
This commit is contained in:
epriestley 2014-11-07 12:26:20 -08:00
parent 8b4a1b693f
commit 5372fb772c
7 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/docs/contributor/bug_reports.diviner
View file

@ -58,7 +58,7 @@ make it more difficult for us to figure out what's going wrong.)
To update Phabricator, use a script like this one: To update Phabricator, use a script like this one:
http://www.phabricator.com/rsrc/install/update_phabricator.sh http://www.phabricator.com/rsrc/install/update_phabricator.sh
This script will require some adjustments depending on how your setup is This script will require some adjustments depending on how your setup is
configured, which webserver you are using, etc. configured, which webserver you are using, etc.
@ -176,7 +176,7 @@ We'll look at any issue report we can find (we monitor IRC, email, GitHub,
StackOverflow, Quora, Facebook and Twitter), but the upstream Maniphest is StackOverflow, Quora, Facebook and Twitter), but the upstream Maniphest is
the authoritative bug tracker and the best place to file: the authoritative bug tracker and the best place to file:
https://secure.phabricator.com/maniphest/task/create/ https://secure.phabricator.com/maniphest/task/create/
If you don't want to file there (or, for example, your bug relates to being If you don't want to file there (or, for example, your bug relates to being
unable to log in or unable to file an issue in Maniphest) you can file on any unable to log in or unable to file an issue in Maniphest) you can file on any

2
src/docs/contributor/feature_requests.diviner
View file

@ -167,7 +167,7 @@ If you think your feature might be a good fit for the upstream, have reasonable
expectations about it, and have a good description of the problem you're trying expectations about it, and have a good description of the problem you're trying
to solve, you're ready to file a feature request: to solve, you're ready to file a feature request:
https://secure.phabricator.com/maniphest/task/create/ https://secure.phabricator.com/maniphest/task/create/
You can file feature requests in places other than Maniphest (like GitHub), but You can file feature requests in places other than Maniphest (like GitHub), but
we can address them far more effectively if you file them in the upstream. we can address them far more effectively if you file them in the upstream.

2
src/docs/contributor/using_oauthserver.diviner
View file

@ -101,7 +101,7 @@ message.
Simply include a query param with the key of "access_token" and the value Simply include a query param with the key of "access_token" and the value
as the earlier obtained access token. For example: as the earlier obtained access token. For example:
https://phabricator.example.com/api/user.whoami?access_token=ykc7ly7vtibj334oga4fnfbuvnwz4ocp https://phabricator.example.com/api/user.whoami?access_token=ykc7ly7vtibj334oga4fnfbuvnwz4ocp
If the token has expired or is otherwise invalid, the client will receive If the token has expired or is otherwise invalid, the client will receive
an error indicating as such. In these cases, the client should re-initiate an error indicating as such. In these cases, the client should re-initiate

4
src/docs/user/installation_guide.diviner
View file

@ -152,7 +152,7 @@ Then you have two options. Either install via PECL (try this first):
**If that doesn't work**, grab the package from PECL directly and follow the **If that doesn't work**, grab the package from PECL directly and follow the
build instructions there: build instructions there:
http://pecl.php.net/package/APC http://pecl.php.net/package/APC
Installing APC is optional but **strongly recommended**, especially on Installing APC is optional but **strongly recommended**, especially on
production hosts. production hosts.
@ -180,7 +180,7 @@ update Phabricator:
For more details, see @{article:Configuration Guide}. You can use a script For more details, see @{article:Configuration Guide}. You can use a script
similar to this one to automate the process: similar to this one to automate the process:
http://www.phabricator.com/rsrc/install/update_phabricator.sh http://www.phabricator.com/rsrc/install/update_phabricator.sh
= Next Steps = = Next Steps =

2
src/docs/user/userguide/arcanist_coverage.diviner
View file

@ -32,7 +32,7 @@ Differential and displayed in the right gutter when viewing diffs.
If you're contributing, libphutil, Arcanist and Phabricator support coverage if If you're contributing, libphutil, Arcanist and Phabricator support coverage if
you install Xdebug: you install Xdebug:
http://xdebug.org/ http://xdebug.org/
It should be sufficient to correctly install Xdebug; coverage information will It should be sufficient to correctly install Xdebug; coverage information will
be automatically enabled. be automatically enabled.

2
src/docs/user/userguide/diffusion.diviner
View file

@ -67,7 +67,7 @@ abbreviate the hash, but note that hash collisions are probable for short prefix
lengths. See this post on the LKML for a historical explanation of Git's lengths. See this post on the LKML for a historical explanation of Git's
occasional internal use of 7-character hashes: occasional internal use of 7-character hashes:
https://lkml.org/lkml/2010/10/28/287 https://lkml.org/lkml/2010/10/28/287
Because 7-character hashes are likely to collide for even moderately large Because 7-character hashes are likely to collide for even moderately large
repositories, Diffusion generally uses either a 16-character prefix (which makes repositories, Diffusion generally uses either a 16-character prefix (which makes

2
src/docs/user/userguide/external_editor.diviner
View file

@ -48,4 +48,4 @@ Then set your "Editor Link" to:
General instructions for configuring some other editors and environments can be General instructions for configuring some other editors and environments can be
found here: found here:
http://wiki.nette.org/en/howto-editor-link http://wiki.nette.org/en/howto-editor-link