Looks like a very interesting solution, see here: http://www.cis.upenn.edu/~bcpierce/unison/
http://www.howtoforge.com/linux_unison On 5/14/07, Sean <[EMAIL PROTECTED]> wrote:
How about Unison and a usb drive. On 5/13/07, Nimrod A. Abing <[EMAIL PROTECTED]> wrote: > On 5/12/07, Ketil Malde <[EMAIL PROTECTED]> wrote: > > > > Justin Bailey wrote: > > > I have a situation which is described perfectly in an email from 2005 > > > (http://lists.osuosl.org/pipermail/darcs-users/2005-March/006425.html). > > > > IIUC, the two sites cannot be reached directly from each other (so http > > or ssh access is out of the question. Would it be possible to have a > > setup with two repos at each site, one local working repo, and one > > mirror of the remote. Ideally, you'd have a procmail setup that applied > > patches automatically (examples on the darcs site, I think), and a > > mirror setup with 'darcs send' target addresses that are distributed to > > both sites. > > > > Given sites A and B and _w for working, _m for mirror, the patch flow > > would look like > > > > darcs pull A_m -> A_w > > (work and record in A_w) > > darcs send A_w -> B_m, A_m > > > > darcs pull B_m -> B_w > > (work and record in B_w) > > darcs send B_w -> A_m, B_m > > > > You'd need to be careful never to 'pull' from or 'push' into the > > mirrors, of course. Would something like this work? > > I have changed my workflow from the one I previously described in the > email cited by the OP. I now follow that same idea suggested by Ketil > above as it allows for better two-way synchronization between > machines. > -- > _nimrod_a_abing_ > > [?] http://abing.gotdns.com > _______________________________________________ > darcs-users mailing list > [email protected] > http://lists.osuosl.org/mailman/listinfo/darcs-users >
-- _nimrod_a_abing_ [?] http://abing.gotdns.com _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
