On Wed, Oct 24, 2001 at 04:31:06PM -0500, Justin Banks wrote:
> > "Dave" == Dave Dykstra <[EMAIL PROTECTED]> writes:
>
> Dave> On Wed, Oct 24, 2001 at 02:26:29PM -0500, Justin Banks wrote:
> >> > "Dave" == Dave Dykstra <[EMAIL PROTECTED]> writes:
> >>
> Dave> The filename paths t
On Wed, Oct 24, 2001 at 02:26:29PM -0500, Justin Banks wrote:
> > "Dave" == Dave Dykstra <[EMAIL PROTECTED]> writes:
>
> Dave> The filename paths that the exclude algorithm sees are relative to the
> Dave> destination path, they do not include it. It should work if you use
> Dave> --in
Justin Banks [[EMAIL PROTECTED]] writes:
> If your suggestion worked, that would be just fine with
> me. Actually, I guess it's fine anyway, I'll just have to maintain
> my patch ;)
This is probably obvious, but just in case it isn't, CVS makes this
fairly trivial (importing the main rsync relea
On Wed, Oct 24, 2001 at 12:42:29PM -0500, Justin Banks wrote:
> > "Dave" == Dave Dykstra <[EMAIL PROTECTED]> writes:
> Dave> The way to recursively delete a single directory while ignoring the
> Dave> rest is:
>
> Dave> mkdir /tmp/empty rsync -a --delete --include "/directorytodelet
On Tue, Oct 23, 2001 at 09:08:25PM -0500, Justin Banks wrote:
> > "Tim" == tim conway <[EMAIL PROTECTED]> writes:
>
> Tim> That's the way it is. If it's really a one-off change, a huge change
> Tim> in your structure, telnet ssh, rsh, and so forth, work really well for
> Tim> dropping
rsync-admin@lists[EMAIL PROTECTED]
That's the way it is. If it's really a one-off change, a huge change in your
structure, telnet ssh, rsh, and so forth, work really well for dropping in and
deleting stuff (unless you're supplying the master, and other systems out of your
control copy
from you). Rsync is optimized for taking a
