Re: Checkin/checkout via 'sneakernet'

On Thu, 2003-11-13 at 11:30, John Allsup wrote:

> Then hack in an 'input' that bypasses the network layer in subversion,
> similarly
> hack in an 'output' that bypasses the network layer. That sort of thing.

Where does the change go when its committed?

You want your working copy to believe it has committed to 'something'.
You then make more changes in the working copy, and commit to
'something' again. You repeat this process a few times.

Then later on, you want 'something' to commit all the saved-up changes
to the true repository.

So whatever 'something' is, it's not just a simple capacitor. It needs
to be smart. It has to be able to collect a bunch of changesets and
manage them as real objects. It also needs to understand the working
copy that they came from, and the repository to which they're destined.

Hey... look... 'something' sure sounds a whole lot like a distributed
repository! :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 13 18:40:38 2003