Skip to content

Commit

Permalink
Minor doc fix - use only binary name
Browse files Browse the repository at this point in the history
This is compatible with the installation guidelines, as the binary will
be in user's PATH
  • Loading branch information
djipko committed Nov 29, 2020
1 parent ec4c20a commit 3b1ecbd
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ and by default it's expected to be stored in a file called `.gbackup.toml` in th
working directory (but is configurable via the -c option). Then you would simply run:

```bash
GMAIL_PASSWORD="mysecretpass" ./gbackup-rs -w 10
GMAIL_PASSWORD="mysecretpass" gbackup-rs -w 10
```

This is recommended for the first back-up as it will pull down email using
Expand All @@ -79,7 +79,7 @@ Exporting the data to a widely used format such as [mbox](http://qmail.org./man/
can be done by running with the `export` subcommand

```bash
./gbackup-rs -c ~/.gbackup.toml export
gbackup-rs -c ~/.gbackup.toml export
```

This will in turn run any export engines configured for each account in the config,
Expand Down
4 changes: 2 additions & 2 deletions src/main.rs
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@
//! working directory (but is configurable via the -c option). Then you would simply run:
//!
//! ```bash
//! GMAIL_PASSWORD="mysecretpass" ./gbackup-rs -w 10
//! GMAIL_PASSWORD="mysecretpass" gbackup-rs -w 10
//! ```
//!
//! This is recommended for the first back-up as it will pull down email using
Expand All @@ -61,7 +61,7 @@
//! can be done by running with the `export` subcommand
//!
//! ```bash
//! ./gbackup-rs -c ~/.gbackup.toml export
//! gbackup-rs -c ~/.gbackup.toml export
//! ```
//!
//! This will in turn run any export engines configured for each account in the config,
Expand Down

0 comments on commit 3b1ecbd

Please sign in to comment.