From: Jim Kingdon <kingdon@panix.com>
To: overseers@sourceware.cygnus.com
Subject: Re: ftp mirrors
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200006111524.LAA14449@panix6.panix.com> (raw)
In-Reply-To: <20000610235503.A8352@shell17.ba.best.com>
> You're suggesting that rsync is clever enough to see two files on
> the server, foo-2000-06-09 and foo-2000-06-10, see that the client
> already has foo-2000-06-09, and make the leap that the -09 and -10
> files are probably pretty close to each other, so do a diff between
> the server's -09 and -10 and send that diff?
If rsync just concatenates the files or something equivalent it should
be able to get this result without a special case (at least some of
the time). See
http://rsync.samba.org/rsync/tech_report/
especially the section on "checksum searching". Of course it would be
good if someone would actually test it to verify this happens in real
world cases like snapshots.
There is hair and possible adverse effects in the cases where rsync
can't do it's magic, but I guess at least in the case of cvsup, we
(well, Jeff anyway :-)) were willing to deal with the hair if Andrew
did the work of actually maintaining the thing.
WARNING: multiple messages have this Message-ID
From: Jim Kingdon <kingdon@panix.com>
To: overseers@sourceware.cygnus.com
Subject: Re: ftp mirrors
Date: Sun, 11 Jun 2000 08:24:00 -0000 [thread overview]
Message-ID: <200006111524.LAA14449@panix6.panix.com> (raw)
Message-ID: <20000611082400.m0-Q75mDSLG79g5MFEalGUcqJYNVzC-G0JqqqGaWhvY@z> (raw)
In-Reply-To: <20000610235503.A8352@shell17.ba.best.com>
> You're suggesting that rsync is clever enough to see two files on
> the server, foo-2000-06-09 and foo-2000-06-10, see that the client
> already has foo-2000-06-09, and make the leap that the -09 and -10
> files are probably pretty close to each other, so do a diff between
> the server's -09 and -10 and send that diff?
If rsync just concatenates the files or something equivalent it should
be able to get this result without a special case (at least some of
the time). See
http://rsync.samba.org/rsync/tech_report/
especially the section on "checksum searching". Of course it would be
good if someone would actually test it to verify this happens in real
world cases like snapshots.
There is hair and possible adverse effects in the cases where rsync
can't do it's magic, but I guess at least in the case of cvsup, we
(well, Jeff anyway :-)) were willing to deal with the hair if Andrew
did the work of actually maintaining the thing.
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200006091545.LAA00938.cygnus.project.sourcemaster@envy.delorie.com>
2000-12-30 6:08 ` Jim Kingdon
2000-06-09 14:53 ` Jim Kingdon
2000-12-30 6:08 ` Andrew Cagney
2000-06-09 22:05 ` Andrew Cagney
2000-12-30 6:08 ` Jason Molenda
2000-06-10 1:02 ` Jason Molenda
2000-12-30 6:08 ` Andrew Cagney
2000-06-10 4:19 ` Andrew Cagney
2000-12-30 6:08 ` Andrew Cagney
2000-06-10 18:03 ` Andrew Cagney
2000-12-30 6:08 ` Jason Molenda
2000-06-10 23:55 ` Jason Molenda
2000-12-30 6:08 ` Jim Kingdon [this message]
2000-06-11 8:24 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
2000-06-11 15:08 ` Jason Molenda
2000-12-30 6:08 ` Jason Molenda
2000-06-10 9:39 ` Jason Molenda
2000-12-30 6:08 ` Jason Molenda
2000-06-10 1:08 ` Jason Molenda
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=200006111524.LAA14449@panix6.panix.com \
--to=kingdon@panix.com \
--cc=overseers@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).