Checkin/checkout via 'sneakernet'

Hi,

I've come up against a situation (a couple of years back) where this sort
of thing
would have been nice. (I coded up a _very_ bad implementation in PERL that
was good
enough for my needs at the time. I concluded that I didn't know enough
about doing
version control and stuff properly.)

Basically this occurs when e.g. you're going home for Christmas, want to
get work
done but don't have internet access, just a PC. (Assume that network
connection
is impossible.)

What I'd like to be able to do is:
   We have two pc's, which I'll call D (for disconnected) and N (for
networked).

   I want to be able to work from D, but retain versioning during this time,
   (though only be able to _use_ versioning after stuff is checked back in.)

   So, I'd like to be able to sit down at N, check out some project and
copy the
   'checkout' to a zipdisk. I'd then like to be able to sit down at D,
insert the
   zip disk, and then complete the checkout to D.

   Working at D, I want to have a 'journal' of 'checkin's which I can copy
back
   to the zip disk, take to N, sit down and then 'batch checking' as if the
checkins
   done at D really went directly to the server.

With respect to the above:
* What are the issues?
* What is feasible?
* What is easily hacked into the client? (clearly no server hacking is
allowed)
* What is possible already?
* What is not possible? (And why?)
* What is not worth the effort? (please don't just say 'the above')

Thanks,

John.

-- 
John Allsup
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org