"Tom Hawkins" <[EMAIL PROTECTED]> writes: > On Thu, Nov 20, 2008 at 9:20 PM, Trent W. Buck <[EMAIL PROTECTED]> wrote: >> "Tom Hawkins" <[EMAIL PROTECTED]> writes: >>> Another thought on performance... Has any one considered an option >>> for darcs to leave the repositories in constant contact with each >>> other? >> >> bzr has a checkout mode that behaves just like svn, in that committing a >> revision (recording a patch) and pushing it to the "parent" repo are a >> single atomic operation (at least as far as the user is concerned). >> >> Is that what you're talking about? Because otherwise it sounds to me >> just like ordinary cron jobs. > > Yes, but without committing the push on the remote machine. Consider > our company's development environment: some of our team is at the > office connected to a high speed LAN, and others are in the field > connected via a slow cell modem. If an engineer in the office records > a patch, and an engineer in the field pulls the patch 3 hours later, > he has to wait. However, if the patch information starts propagating > to the rest of the team at the time of record, when someone does a > pull it could appear to be instantaneous.
I don't see why that's not achievable with a cron job -- note that it doesn't have to pull the patch into the field operative's "real" repo, it can just be pulled into a temporary one. That would seed ~/.darcs/cache. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
