# HG changeset patch # User Thomas De Schampheleire # Date 1428176722 -7200 # Node ID e5ab200892e3c8de4315e4846bf0c67d5a1cf09f # Parent 584693b3deb07e6929c8d18bcebb2f5aaa46b4e1 docs/usage: reword section 'cloning remote repositories' diff -r 584693b3deb0 -r e5ab200892e3 docs/usage/general.rst --- a/docs/usage/general.rst Sat Apr 04 21:39:07 2015 +0200 +++ b/docs/usage/general.rst Sat Apr 04 21:45:22 2015 +0200 @@ -122,7 +122,7 @@ Cloning remote repositories --------------------------- -Kallithea has the ability to clone remote repos from given remote locations. +Kallithea has the ability to clone repositories from given remote locations. Currently it supports the following options: - hg -> hg clone @@ -130,15 +130,15 @@ - git -> git clone -.. note:: svn -> hg cloning requires tge ``hgsubversion`` library to be installed. +.. note:: svn -> hg cloning requires the ``hgsubversion`` library to be + installed. -If you need to clone repositories that are protected via basic auth, you -might pass the url with stored credentials inside, e.g., -``http://user:passw@remote.server/repo``, Kallithea will try to login and clone -using the given credentials. Please take note that they will be stored as -plaintext inside the database. Kallithea will remove auth info when showing the -clone url in summary page. - +If you need to clone repositories that are protected via basic authentication, +you can pass the credentials in the URL, e.g. +``http://user:passw@remote.server/repo``. Kallithea will then try to login and +clone using the given credentials. Please note that the given credentials will +be stored as plaintext inside the database. However, the authentication +information will not be shown in the clone URL on the summary page. Specific features configurable in the Admin settings