diff options
| author | Patrick Ohly <patrick.ohly@intel.com> | 2012-07-10 07:11:05 +0000 |
|---|---|---|
| committer | Patrick Ohly <patrick.ohly@intel.com> | 2012-07-10 07:59:32 +0000 |
| commit | 34f67dfec150b47cbd4b6adf3b908586c04b67dd (patch) | |
| tree | 0b198cb6fea312f318540a524396b6ab47103c2e | |
| parent | fc82807dd7136479ad9eb5961832042b2bde9e84 (diff) | |
NEWS: fixed spelling and truncation
Copying long lines from git log output truncated them at the width
of the shell.
| -rw-r--r-- | NEWS | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -98,7 +98,7 @@ Details: Now SyncEvolution's WebDAV backend will print a message like this before going to sleep until it is time to retry: - [INFO @googlecalendar] operation temporarily (?) failed, going to retry in 5.0s before giving up in 1 + [INFO @googlecalendar] operation temporarily (?) failed, going to retry in 5.0s before giving up in 18.4s: PROPFIND: Neon error code 1: 401 Unauthorized The uncertainty comes from several factors. In this example, the 401 might indicate a permanent problem (wrong credentials), or it could be @@ -109,7 +109,7 @@ Details: past. Otherwise it gives up immediately. Another dubious example are name server lookup errors. They can be - ermanent (wrong host name) or temporary (name server + permanent (wrong host name) or temporary (name server down). SyncEvolution errs on the side of retrying, to avoid interrupting an operation which still has a chance to continue. @@ -424,7 +424,7 @@ Details: ^C[INFO] Asking to suspend... [INFO] Press CTRL-C again quickly (within 2s) to stop immediately (can cause problems in the future!) ^C[INFO] Aborting immediately ... - [ERROR] error code from SyncEvolution aborted on behalf of user (local, status 20017): aborting as requested by u + [ERROR] error code from SyncEvolution aborted on behalf of user (local, status 20017): aborting as requested by user It would be good to make the CTRL-C handling code aware that it can abort immediately instead of doing the intermediate "asking to suspend" |