mirror of
https://github.com/rclone/rclone.git
synced 2025-12-11 22:14:05 +01:00
docs: fix markdownlint issue md012/no-multiple-blanks
This commit is contained in:
@@ -1,5 +1,3 @@
|
||||
|
||||
|
||||
[<img src="https://rclone.org/img/logo_on_light__horizontal_color.svg" width="50%" alt="rclone logo">](https://rclone.org/#gh-light-mode-only)
|
||||
[<img src="https://rclone.org/img/logo_on_dark__horizontal_color.svg" width="50%" alt="rclone logo">](https://rclone.org/#gh-dark-mode-only)
|
||||
|
||||
|
||||
@@ -43,4 +43,3 @@ Bugs are stored in rclone's GitHub project:
|
||||
|
||||
* [Reported bugs](https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug)
|
||||
* [Known issues](https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Known+Problem%22)
|
||||
|
||||
|
||||
@@ -5847,4 +5847,3 @@ Point release to fix hubic and azureblob backends.
|
||||
## v0.00 - 2012-11-18
|
||||
|
||||
* Project started
|
||||
|
||||
|
||||
@@ -1640,8 +1640,6 @@ returned from the rc call [core/stats](/rc/#core-stats).
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
### --low-level-retries int
|
||||
|
||||
This controls the number of low level retries rclone does.
|
||||
@@ -3188,7 +3186,6 @@ $ rclone lsd MYS3:
|
||||
-1 2016-09-21 12:54:21 -1 my-bucket
|
||||
```
|
||||
|
||||
|
||||
Note that you can only set the options of the immediate backend,
|
||||
so RCLONE_CONFIG_MYS3CRYPT_ACCESS_KEY_ID has no effect, if myS3Crypt is
|
||||
a crypt remote based on an S3 remote. However RCLONE_S3_ACCESS_KEY_ID will
|
||||
|
||||
@@ -49,7 +49,6 @@ e.g.
|
||||
|
||||
rclone sync --interactive drive:Folder s3:bucket
|
||||
|
||||
|
||||
### Using rclone from multiple locations at the same time ###
|
||||
|
||||
You can use rclone from multiple places at the same time if you choose
|
||||
@@ -122,7 +121,6 @@ possibilities. So, on Linux, you may end up with code similar to
|
||||
export HTTP_PROXY=$http_proxy
|
||||
export HTTPS_PROXY=$http_proxy
|
||||
|
||||
|
||||
Note: If the proxy server requires a username and password, then use
|
||||
|
||||
export http_proxy=http://username:password@proxyserver:12345
|
||||
@@ -204,7 +202,6 @@ If you are using `systemd-resolved` (default on Arch Linux), ensure it
|
||||
is at version 233 or higher. Previous releases contain a bug which
|
||||
causes not all domains to be resolved properly.
|
||||
|
||||
|
||||
The Go resolver decision can be influenced with the `GODEBUG=netdns=...`
|
||||
environment variable. This also allows to resolve certain issues with
|
||||
DNS resolution. On Windows or MacOS systems, try forcing use of the
|
||||
|
||||
@@ -526,7 +526,6 @@ matching `secret*.jpg` and including `file2.avi`. It also includes
|
||||
everything in the directory `dir` at the root of `remote`, except
|
||||
`remote:dir/Trash` which it excludes. Everything else is excluded.
|
||||
|
||||
|
||||
E.g. for an alternative `filter-file.txt`:
|
||||
|
||||
- secret*.jpg
|
||||
@@ -891,7 +890,6 @@ applied](#how-filter-rules-work) for more details - these flags work
|
||||
in an identical way to the file name filtering flags, but instead of
|
||||
file name patterns have metadata patterns.
|
||||
|
||||
|
||||
## Common pitfalls
|
||||
|
||||
The most frequent filter support issues on
|
||||
@@ -900,4 +898,3 @@ the [rclone forum](https://forum.rclone.org/) are:
|
||||
* Not using paths relative to the root of the remote
|
||||
* Not using `/` to match from the root of a remote
|
||||
* Not using `**` to match the contents of a directory
|
||||
|
||||
|
||||
@@ -107,5 +107,3 @@ The GUI is being developed in the: [rclone/rclone-webui-react repository](https:
|
||||
Bug reports and contributions are very welcome :-)
|
||||
|
||||
If you have questions then please ask them on the [rclone forum](https://forum.rclone.org/).
|
||||
|
||||
|
||||
|
||||
@@ -339,7 +339,6 @@ Note that this is controlled by [community maintainer](https://github.com/bouken
|
||||
|
||||
[](https://snapcraft.io/rclone)
|
||||
|
||||
|
||||
## Source installation {#source}
|
||||
|
||||
Make sure you have git and [Go](https://golang.org/) installed.
|
||||
|
||||
@@ -29,4 +29,3 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
||||
THE SOFTWARE.
|
||||
```
|
||||
|
||||
|
||||
@@ -2548,4 +2548,3 @@ for more info on how to use the profiling and for a general overview
|
||||
see [the Go team's blog post on profiling go programs](https://blog.golang.org/profiling-go-programs).
|
||||
|
||||
The profiling hook is [zero overhead unless it is used](https://stackoverflow.com/q/26545159/164234).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user