From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: [9fans] cpdir
Date: Mon, 29 Sep 2003 23:03:35 +0900 [thread overview]
Message-ID: <B7AFB2F0-F285-11D7-B085-000393A941BC@ar.aichi-u.ac.jp> (raw)
Hello 9fans.
cpdir is updated to ver.1.4
-x option is added
#
# Usage
#
Usage: cpdir [-vugRm] [-l file] [-x xfile] srcdir destdir [path ...]
Options and arguments:
-v: verbose
-u: copy owner info
-g: copy group info
-R: remove redundant files and directories in dstdir
-m: merge
-l file:
A file of path list to be processed.
Path list must be a path per line.
-x xfile
A file of path list that should not be copied.
Path list must be a path per line.
Rc style globe expression is allowed for the path.
In the matching rule, "/" is simply a character.
srcdir:
source dir from which copy is made.
destdir:
destination dir in which copy is made.
path ... : pathes in source to be processed.
Function:
`cpdir' makes effort to make a copy of file in srcdir
to dstdir. Those that are copied are:
- contents
- modification time
- permissions
- group if possible. (under -g option)
- owner if possible. (under -u option)
What happens if there are files of same name
in both source and destination?
Let s.mtime and d.mtime be modification time of source
and destination respectively. Then `cpdir' copies:
- contents (if s.mtime > d.mtime)
- modification time (if source.mtime > destination.mtime)
- permissions (if s.mtime >= d.mtime)
- group (under -g option, if s.mtime >= d.mtime)
- owner if possible. (under -u option, if s.mtime >= d.mtime)
With -R option, `cpdir' removes files and directories
in destination that are non-existent in source.
Kenji Arisawa
E-mail: arisawa@ar.aichi-u.ac.jp
NOTE: replace "@ar." by "@"
next reply other threads:[~2003-09-29 14:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 14:03 Kenji Arisawa [this message]
2003-09-29 20:44 ` Kenji Arisawa
2003-09-29 21:14 ` boyd
2007-03-21 15:44 Devon H. O'Dell
2007-03-21 17:15 ` Abhey Shah
2007-03-21 17:22 ` C H Forsyth
2007-03-21 20:03 ` David Leimbach
2007-03-22 11:15 ` Abhey Shah
2007-03-22 16:14 ` Paul Lalonde
2007-03-22 17:55 ` David Leimbach
2007-03-22 17:54 ` David Leimbach
2007-03-26 13:06 Russ Cox
2007-03-26 13:10 ` Gorka Guardiola
2007-03-26 13:26 ` Gabriel Diaz
2007-03-26 13:31 ` erik quanstrom
2007-03-26 15:46 ` arisawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B7AFB2F0-F285-11D7-B085-000393A941BC@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).