From 1e7020687a97e84c712a0aed35ed96d098832744 Mon Sep 17 00:00:00 2001 From: Ciaran Gultnieks Date: Sun, 7 Aug 2011 16:16:54 +0100 Subject: [PATCH] Remove obsolete (after today's earlier commits) documentation paragraph --- README | 7 ------- fdroid.texi | 7 ------- 2 files changed, 14 deletions(-) diff --git a/README b/README index 488d45c2..9439d8cc 100644 --- a/README +++ b/README @@ -97,13 +97,6 @@ values are: The repository location. Usually a git: or svn: URL. -Normally the repository is checked out once for the application, then moved -to a particular revision/commit/tag for each build version. For an SVN -repository though, this behaviour can be changed by appending a * to the -repository URL - in this case the repository is checked out once per build -version, with the subdir parameter in place of the *. This can be beneficial -when dealing with very large SVN repositories. - For a Subversion repo that requires authentication, you can precede the repo URL with username:password@ and those parameters will be passed as --username and --password to the SVN checkout command. diff --git a/fdroid.texi b/fdroid.texi index 048e40ae..e3a3e89e 100644 --- a/fdroid.texi +++ b/fdroid.texi @@ -297,13 +297,6 @@ values are: The repository location. Usually a git: or svn: URL. -Normally the repository is checked out once for the application, then moved -to a particular revision/commit/tag for each build version. For an SVN -repository though, this behaviour can be changed by appending a * to the -repository URL - in this case the repository is checked out once per build -version, with the subdir parameter in place of the *. This can be beneficial -when dealing with very large SVN repositories. - For a Subversion repo that requires authentication, you can precede the repo URL with username:password@ and those parameters will be passed as @option{--username} and @option{--password} to the SVN checkout command. -- 2.30.2