kup.1: document the handling of pathnames

Document the way the kup client handles pathnames.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>

1 files changed, 12 insertions, 0 deletions

diff --git a/kup.1 b/kup.1
index 288c704..6133744 100644
--- a/kup.1
+++ b/kup.1
@@ -112,6 +112,18 @@ all the compression formats are linked together.
 Delete the file or directory \fIold_path\fP.  For a file, the
 \fI.sign\fP files are also deleted, and for compressed files, all the
 compression formats are deleted together.
+.SH PATHNAME HANDLING
+Remote (server) pathnames all need to be absolute paths, starting with
+a slash (/).  The sole exception is \fInew_path\fP for the \fBmv\fP
+and \fBlink\fP commands, which if it is not absolute is taken to be
+relative to the \fIold_path\fP minus the final component.  Similarly,
+if \fInew_path\fP ends in a slash then the final component of
+\fIold_path\fP will be appended.
+.PP
+For the \fPput\fP command, except when \fB\-\-tar\fP or \fB\-\-diff\fP
+is specified, if the \fIremote_path\fP ends in a slash then the
+final (filename) component of \fIlocal_file\fP will be appended to the
+final pathname.
 .SH AUTHOR
 Written by H. Peter Anvin <hpa@zytor.com>.
 .SH COPYRIGHT